Re: [GENERAL] pg_upgrade ?deficiency - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [GENERAL] pg_upgrade ?deficiency
Date
Msg-id 20131127001942.GA12397@momjian.us
Whole thread Raw
In response to Re: [GENERAL] pg_upgrade ?deficiency  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: [GENERAL] pg_upgrade ?deficiency  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
On Tue, Nov 26, 2013 at 03:25:44PM -0800, Kevin Grittner wrote:
> Bruce Momjian <bruce@momjian.us> wrote:
> 
> > How are we handling breakage of pg_dump, not pg_dumpall?
> 
> That was discussed.  Do you have something to add?

I am confused what we are patching.  Are we patching pg_dump,
pg_dumpall, or both?  Can I see the full patch?  Are we propagating
other settings from pg_dump to pg_dumpall, like statement_timeout?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist
Next
From: Tom Lane
Date:
Subject: Re: lock on object is already held