partitioning an existing table - Mailing list pgsql-performance

From Robert Blayzor
Subject partitioning an existing table
Date
Msg-id D8C4F7BD-FECE-4ABB-9B16-5A764ADBD5DF@inoc.net
Whole thread Raw
Responses Re: partitioning an existing table  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-performance
The docs claim that the master table “should” be empty. It it possible to just create child tables off an existing
mastertable 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, then drop the
indexesas well. 

Fully understanding that data needs to be placed in the right child tables. Data outside of those child ranges would
remainas “old data” in the master table. 


Just trying to grab if that’s an acceptable migration of live data from a single large table and move into
partitioning.Think of it as a very large table of cyclic data that ages out. New data in child tables while removing
datafrom the master table over time. 

--
inoc.net!rblayzor
XMPP: rblayzor.AT.inoc.net
PGP:  https://inoc.net/~rblayzor/
















pgsql-performance by date:

Previous
From: pinker
Date:
Subject: Re: Table performance with millions of rows (partitioning)
Next
From: Justin Pryzby
Date:
Subject: Re: partitioning an existing table