From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tom Cassidy <tcassidy@mossridge.com.au>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #15602: pg_dump archive items not in correct section order
In-reply-to: <23ab4c34-f612-ad5f-5df8-fae676952c73@mossridge.com.au>
References: <201901231644.rh46t3asx75y@alvherre.pgsql>
 <7655.1549301072@sss.pgh.pa.us>
 <23ab4c34-f612-ad5f-5df8-fae676952c73@mossridge.com.au>
Comments: In-reply-to Tom Cassidy <tcassidy@mossridge.com.au>
	message dated "Tue, 05 Feb 2019 01:42:09 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4466.1549331079.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 04 Feb 2019 20:44:39 -0500
Message-ID: <4467.1549331079@sss.pgh.pa.us>
Precedence: bulk

Tom Cassidy <tcassidy@mossridge.com.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-mes=
sing-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