Re: partitioning an existing table - efficient pg_dump

2017-12-30 Thread Justin Pryzby
On Sat, Dec 30, 2017 at 09:19:05AM -0500, Robert Blayzor wrote: > On Dec 30, 2017, at 12:38 AM, Justin Pryzby wrote: > > BTW depending on your requirements, it may be possible to make pg_dump much > > more efficient. For our data, it's reasonable to assume that a table is > > "final" if its cons

Re: partitioning an existing table

2017-12-30 Thread Robert Blayzor
On Dec 30, 2017, at 12:38 AM, Justin Pryzby wrote: > For inheritance (available in and before PG10), the parent may be nonempty, > which works fine, although someone else might find it unintuitive. (Does the > doc actually say "should" somewhere ?) Well it doesn’t say should, but says “normally”

Re: partitioning an existing table

2017-12-29 Thread Justin Pryzby
On Fri, Dec 29, 2017 at 11:37:56PM -0500, Robert Blayzor wrote: > The docs claim that the master table “should” be empty. It it possible to > just create child tables off an existing master table with data, then just > inserting data into the new child tables. > > THe plan would be to keep data

partitioning an existing table

2017-12-29 Thread Robert Blayzor
The docs claim that the master table “should” be empty. It it possible to just create child tables off an existing master table with data, then just inserting data into the new child tables. THe plan would be to keep data in the master table and purge it over time until it’s eventually empty, t