Redshift is translating 'dbo' schema name in to 'public' schema name.

0

We have two Redshift clusters. One cluster updated to version 1.0.44126 over the weekend. After that, we started experiencing failures in some data extract processes. The error was: ERROR: schema "dbo" does not exist

Sure enough, after reviewing the queries we had inadvertently used dbo instead of public in the schema name. However, it worked for months prior to this latest Redshift version. I cannot find any information on version 1.0.44126. I cannot find any feature that might translate these schema names transparently.

Why is Redshift doing this?

I can reproduce the behavior on cluster version 1.0.43931.

create table public.test_table ( test integer );
select * from dbo.test_table;
drop table dbo.test_table;

The above all succeeds on cluster version 1.0.43931 and fails on 1.0.44126.

asked a year ago276 views
1 Answer
0

I just tested with 1.0.44903 and your test case appears to work again. I highly recommend you do not continue the practice of using "dbo" as a synonym for "public". This appears to be an undocumented feature which could be removed again in the future.

profile pictureAWS
EXPERT
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions