| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: reload-through-the-top-parent switch the partition table |
| Date: | 2017-08-01 22:25:38 |
| Message-ID: | CA+TgmoZM8f27hVFhfkNzXo2dzu8oTG-2rbCrX=eWOiD6sBgSqg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 1, 2017 at 5:34 AM, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-01 22:52:32 | Re: BUG #14758: Segfault with logical replication on a function index |
| Previous Message | Robert Haas | 2017-08-01 22:21:52 | Re: Adding support for Default partition in partitioning |