Peter Eisentraut wrote: > On 5/12/17 14:23, Robert Haas wrote: > > One alternative would be to change the way that we dump and restore > > the data. Instead of dumping the data with the individual partitions, > > dump it all out for the parent and let tuple routing sort it out at > > restore time. > > I think this could be a pg_dump option. One way it dumps out the > partitions, and another way it recomputes the partitions. I think that > could be well within pg_dump's mandate.
I was thinking the same, but enable that option automatically for hash partitioning. Each partition is still dumped separately, but instead of referencing the specific partition in the TABLE DATA object, reference the parent table. This way, the restore can still be parallelized, but tuple routing is executed for each tuple. > (cough ... logical replication ... cough) I think for logical replication the tuple should appear as being in the parent table, not the partition. No? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers