Re: [HACKERS] reload-through-the-top-parent switch the partition table - Mailing list pgsql-hackers

From Rushabh Lathia
Subject Re: [HACKERS] reload-through-the-top-parent switch the partition table
Date
Msg-id CAGPqQf1YpORjb=NVazxqA3O7iOYjETRSqf0WkrtricS9JbXkXA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] reload-through-the-top-parent switch the partition table  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] reload-through-the-top-parent switch the partition table  (Robert Haas <robertmhaas@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: [HACKERS] INSERT ON CONFLICT and partitioned tables
Next
From: Zeray Kalayu
Date:
Subject: Re: [HACKERS] On Complex Source Code Reading Strategy