Re: BUG #15602: pg_dump archive items not in correct section order

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tom Cassidy <tcassidy(at)mossridge(dot)com(dot)au>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15602: pg_dump archive items not in correct section order
Date: 2019-02-05 01:44:39
Message-ID: 4467.1549331079@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Cassidy <tcassidy(at)mossridge(dot)com(dot)au> writes:
> On 5/2/19 4:24 am, Tom Lane wrote:
>> Tom, are you in a position to rebuild pg_dump with this fix applied,
>> and see if it cures your original case as well as the simplified one?

> I downloaded the git source and built postgres from REL_11_STABLE branch
> using the instructions at
> https://blog.2ndquadrant.com/testing-new-postgresql-versions-without-messing-up-your-install/.
> Your patch looked like it was already applied to this branch so I
> didn't apply it.

Yeah, I committed it a couple hours ago --- "git log" would confirm
whether you had it or not.

> Running pg_dump from the patched version I didn't notice any warning
> output on either the original database or the simplified test case
> database, so it appears that this patch solves the issue.

Cool, thanks for checking!

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Saul, Jean Paolo 2019-02-05 04:39:18 Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes
Previous Message Tom Cassidy 2019-02-05 01:42:09 Re: BUG #15602: pg_dump archive items not in correct section order