Re: pg_dump and search_path
| От | Adrian Klaver |
|---|---|
| Тема | Re: pg_dump and search_path |
| Дата | |
| Msg-id | 4f8a9e35-0797-ddf8-ba1a-68b65eb7d2ec@aklaver.com обсуждение |
| Ответ на | Re: pg_dump and search_path (Ryan Lambert <ryan@rustprooflabs.com>) |
| Ответы |
Re: pg_dump and search_path
|
| Список | pgsql-general |
On 7/10/19 1:19 PM, Ryan Lambert wrote:
> I had a similar problem and was able to being the command with the
> search_path to work around it. I did this on Linux and it looks like
> you are on Windows but I maybe you can do something similar that will work?
>
> PGOPTIONS='-c search_path=staging, transient, pg_catalog'
Not sure how that worked:
export PGOPTIONS="-c search_path=public"
psql -d test -U postgres
psql (11.4)
Type "help" for help.
test_(postgres)# show search_path;
search_path
-------------
public
test_(postgres)# SELECT pg_catalog.set_config('search_path', '', false);
set_config
------------
(1 row)
test_(postgres)# show search_path;
search_path
-------------
(1 row)
>
>
> *Ryan Lambert*
> RustProof Labs
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: