Re: pg_dump and search_path - Mailing list pgsql-general

From David G. Johnston
Subject Re: pg_dump and search_path
Date
Msg-id CAKFQuwZ+s3chtdwhNPG5HZSaKx55qkfCWLY+q1LDdWpw2FGkLA@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump and search_path  ("Igal @ Lucee.org" <igal@lucee.org>)
Responses Re: pg_dump and search_path  ("Igal @ Lucee.org" <igal@lucee.org>)
List pgsql-general
On Tue, Jul 9, 2019 at 7:41 AM Igal @ Lucee.org <igal@lucee.org> wrote:
search_path is not set int he config, but rather with ALTER DATABASE SET
search_path TO ... but I have executed that prior to the RESTORE on the
target database.  Would it make a difference if I set it in the config?

What is your restore command then?  Because if you are dropping and recreating the same named database the ALTER DATABASE SET command is going to be lost with the drop since it is associated to an OID and not just the name.  By placing the search_path into postgres.conf you avoid that issue altogether.

But, yes, objects saved to the database should usually have schema qualifications (which gets a bit messy with custom operators).  search_path reliance should probably be reserved to interactive use or at worse client supplied queries.

David J.

pgsql-general by date:

Previous
From: "Igal @ Lucee.org"
Date:
Subject: Re: pg_dump and search_path
Next
From: "Igal @ Lucee.org"
Date:
Subject: Re: pg_dump and search_path