Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_dump and search_path - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump and search_path
Date
Msg-id CA+Tgmob8hLzTEKUjoYwpgLxdY1SZYUNDzKYCb4nMPBA1hySHFg@mail.gmail.com
Whole thread Raw
In response to pg_dump and search_path  ("Steve Thames" <sthames42@gmail.com>)
Responses Re: pg_dump and search_path  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Mon, Aug 10, 2015 at 1:10 PM, Steve Thames <sthames42@gmail.com> wrote:
> Please consider making the arbitrary determination of search_path by pg_dump
> an optional behavior. Or better yet, just have it generate a backup that
> accurately reflects the database it is backing up.

Hmm, I don't think it's a question of making it optional.  I think the
current behavior is just a bug, and should be fixed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Intentional usage of old style function declarations?
Next
From: Tom Lane
Date:
Subject: Re: pg_dump and search_path