Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
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>
Date: 2019-02-05T01:44:39Z
Lists: pgsql-bugs 
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

Commits

  1. Fix dumping of matviews with indirect dependencies on primary keys.

  2. Fix dumping of a materialized view that depends on a table's primary key.