From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: pg_dump directory format and proper ordering
In-reply-to: 
 <CAOC+FBU9K=RGWxphKU41h+dJ0MjponR-hzUE56Xjk7n0aPagOw@mail.gmail.com>
References: 
 <CAOC+FBWRLmJDBx6YewbXZvqTzxQgFJ1ybAykjw95aiR90EBk=g@mail.gmail.com>
 <1832919.1623376575@sss.pgh.pa.us>
 <CAOC+FBU9K=RGWxphKU41h+dJ0MjponR-hzUE56Xjk7n0aPagOw@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Thu, 10 Jun 2021 20:37:17 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1838437.1623383681.1@sss.pgh.pa.us>
Date: Thu, 10 Jun 2021 23:54:41 -0400
Message-ID: <1838438.1623383681@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1838438.1623383681%40sss.pgh.pa.us>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> Is there a potential issue when restoring in parallel?

Not supposed to be ...

> I notice for example it fails to re-create some mat views I have in schema
> B as they query from some table in schema A that hasn't been created yet at
> that moment.

You can break it with user-defined functions, because pg_dump can't
really see into the function bodies to understand what they might
reference.  But a matview that doesn't contain anything like that
should Just Work.  If you have a counterexample (against a reasonably
recent PG version), please file a bug report.

			regards, tom lane