Re: reload-through-the-top-parent switch the partition table
Rushabh Lathia <rushabh.lathia@gmail.com>
From: Rushabh Lathia <rushabh.lathia@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-02T05:01:40Z
Lists: pgsql-hackers
On Wed, Aug 2, 2017 at 3:55 AM, Robert Haas <robertmhaas@gmail.com> wrote: > On Tue, Aug 1, 2017 at 5:34 AM, Rushabh Lathia <rushabh.lathia@gmail.com> > wrote: > > My colleague Robert and I had doubt about the order in of TABLE > > and TABLE_DATA. We thought earlier that reload-thought-root might > > might not solve the purpose which has been discussed in the above > > mentioned thread. But later looking into code I realize the sort order > > for DO_TABLE and DO_TABLE_DATA are different, so we don't need > > to worry about that issue. > > Hmm. Does that mean that table data restoration will *absolutely > always* follow all CREATE TABLE commands, or is that something that's > *normally* true but potentially false if dependency sorting switches > things around? > > Looking at the dbObjectTypePriority comments that seems like data restoration will *absolutely always* follow all CREATE TABLE commands. -- > Robert Haas > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > Thanks, Rushabh Lathia www.EnterpriseDB.com
Commits
-
pg_dump: Add a --load-via-partition-root option.
- 23d7680d04b9 11.0 landed
-
Improve pg_dump's dependency-sorting logic to enforce section dump order.
- a1ef01fe163b 9.3.0 cited