Re: pg_dump and search_path

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Steve Thames <sthames42(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump and search_path
Date: 2015-08-11 17:10:40
Message-ID: CA+Tgmob8hLzTEKUjoYwpgLxdY1SZYUNDzKYCb4nMPBA1hySHFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 10, 2015 at 1:10 PM, Steve Thames <sthames42(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-08-11 17:23:19 Re: pg_dump and search_path
Previous Message Tom Lane 2015-08-11 17:07:43 Re: Intentional usage of old style function declarations?