partitioning an existing table

From: Robert Blayzor <rblayzor(dot)bulk(at)inoc(dot)net>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: partitioning an existing table
Date: 2017-12-30 04:37:56
Message-ID: D8C4F7BD-FECE-4ABB-9B16-5A764ADBD5DF@inoc.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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, then drop the indexes as well.

Fully understanding that data needs to be placed in the right child tables. Data outside of those child ranges would remain as “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 data from the master table over time.

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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Justin Pryzby 2017-12-30 05:38:21 Re: partitioning an existing table
Previous Message pinker 2017-12-28 02:22:14 Re: Table performance with millions of rows (partitioning)