Re: Prefixing schema name - Mailing list pgsql-general

From Tiffany Thang
Subject Re: Prefixing schema name
Date
Msg-id CAB_W-NNQ960er4g3Bpx7MzJo781DPAzHTEFv1KecfJD_-Atk2A@mail.gmail.com
Whole thread Raw
In response to Re: Prefixing schema name  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
List pgsql-general
Thanks David and Achilleas. This is no longer an issue. The table previously went to the public schema. I'm not sure what I did. Anyway, without a prefix, it defaults to the current schema.

On Thu, Mar 8, 2018 at 2:02 AM, Achilleas Mantzios <achill@matrix.gatewaynet.com> wrote:
On 08/03/2018 01:13, David G. Johnston wrote:
On Wed, Mar 7, 2018 at 4:05 PM, Tiffany Thang <tiffanythang@gmail.com> wrote:
The search_path configuration works only for queries.

​Um....


"​A CREATE command specifying an unqualified object name creates the object in the current schema (the one at the front of the search path, which can be determined with the function current_schema)"


In pg_dump relies heavily on search_path for all CREATE statements.


For example:
Is there a way to run the create/insert statements below without prefixing the schema name, user1?

As the user, user1:
Create table user1.table1 (id int);
Insert into user1.table1 values (1);

​Just omitting "user1" and seeing what happens would be informative.  You should find it does exactly what you think - namely because the default search_path will cause "user1" to appear first.

Insert is more similar to Select than it is to Create - the object being inserted into must already exist

David J.
​​


-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: What is the meaning of pg_restore output?
Next
From: Adrian Klaver
Date:
Subject: Re: JDBC connectivity issue