Re: pg_dump and search_path

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: pg_dump and search_path
Дата
Msg-id CAKFQuwZ+s3chtdwhNPG5HZSaKx55qkfCWLY+q1LDdWpw2FGkLA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_dump and search_path  ("Igal @ Lucee.org" <igal@lucee.org>)
Ответы Re: pg_dump and search_path  ("Igal @ Lucee.org" <igal@lucee.org>)
Список 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 по дате отправления:

Предыдущее
От: "Igal @ Lucee.org"
Дата:
Сообщение: Re: pg_dump and search_path
Следующее
От: "Igal @ Lucee.org"
Дата:
Сообщение: Re: pg_dump and search_path