| From: | Tom Cassidy <tcassidy(at)mossridge(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "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:42:09 |
| Message-ID: | 23ab4c34-f612-ad5f-5df8-fae676952c73@mossridge.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
>
> regards, tom lane
Hi Tom,
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.
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.
I ran the pg_dump as plain-text SQL output format, and there were no
differences in the generated SQL between the old pg_dump and the patched
pg_dump, except for the pg_dump version string.
Regards,
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-05 01:44:39 | Re: BUG #15602: pg_dump archive items not in correct section order |
| Previous Message | Saul, Jean Paolo | 2019-02-05 00:51:03 | Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes |