Horton
Menu

Re: Bug in -c CLI option of pg_dump/pg_restore

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Guillaume Lelarge <guillaume@lelarge.info>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-10-19T18:30:53Z
Lists: pgsql-hackers 
On Thu, Oct 18, 2012 at 11:19 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Robert Haas escribió:
>> On Tue, Oct 16, 2012 at 10:31 AM, Guillaume Lelarge
>> <guillaume@lelarge.info> wrote:
>> > Any comments on this?
>>
>> I'm not sure I'd want to back-patch this, since it is a behavior
>> change, but I do think it's probably a good idea to change it for 9.3.
>
> Hm, but the bug is said to happen only in 9.2, so if we don't backpatch
> we would leave 9.2 alone exhibiting this behavior.

Oh, yeah.  I missed that.  But then shouldn't we start by identifying
which commit broke it before we decide on a fix?

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Rewrite --section option to decouple it from --schema-only/--data-only.