From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tom Cassidy <tcassidy@mossridge.com.au>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #15602: pg_dump archive items not in correct section order
Date: Mon, 04 Feb 2019 20:44:39 -0500
Message-ID: <4467.1549331079@sss.pgh.pa.us> (raw)
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>
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-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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tcassidy@mossridge.com.au, alvherre@2ndquadrant.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15602: pg_dump archive items not in correct section order
In-Reply-To: <4467.1549331079@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox