On 04/08/2018 11:01 AM, Rory Campbell-Lange wrote:
Thanks for your comprehensive response, Adrian.
Fair enough. It is however a tedious problem to resolve in a large
code base and it would be cool to have a new "--set-search-path"
option to pg_dump to override it.
From other posts that cove
Thanks for your comprehensive response, Adrian.
On 08/04/18, Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 04/08/2018 03:40 AM, Rory Campbell-Lange wrote:
> > On 07/04/18, Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> > > > (I'm aware that the reasons behind the change made to the dum
On 04/08/2018 03:40 AM, Rory Campbell-Lange wrote:
On 07/04/18, Adrian Klaver (adrian.kla...@aklaver.com) wrote:
(I'm aware that the reasons behind the change made to the dump format
due to CVE-2018-1058 are set out here:
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Se
On 07/04/18, Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> > (I'm aware that the reasons behind the change made to the dump format
> > due to CVE-2018-1058 are set out here:
> > https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path)
> >
>
> > Additionally we som
On 04/07/2018 12:27 PM, Rory Campbell-Lange wrote:
Hi
Following an upgrade to 9.5.12, we cannot restore some of our databases
due to a schema qualification issue introduced in the new postgres
version of pg_dump.
Specifically, the problem line is the addition of :
SELECT pg_catalog.set_co
