Re: pg_dump and search_path

From: Ryan Lambert <ryan(at)rustprooflabs(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump and search_path
Date: 2019-07-10 20:19:09
Message-ID: CAN-V+g9sopbD5uuRhYieHroqumHWJewRV4HKzByZOegxSh+ZuQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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'

*Ryan Lambert*
RustProof Labs

>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-07-10 21:11:18 Re: pg_dump and search_path
Previous Message Bruce Momjian 2019-07-10 18:38:23 Re: DRY up GUI wiki pages