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
Date: Thu, 10 Jun 2021 23:54:41 -0400
Message-ID: <1838438.1623383681@sss.pgh.pa.us> (raw)
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>
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
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, wells.oliver@gmail.com
Subject: Re: pg_dump directory format and proper ordering
In-Reply-To: <1838438.1623383681@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