From: Robert Blayzor <rblayzor.bulk@inoc.net>
To: pgsql-performance@lists.postgresql.org
Subject: partitioning an existing table
Date: Fri, 29 Dec 2017 23:37:56 -0500
Message-ID: <D8C4F7BD-FECE-4ABB-9B16-5A764ADBD5DF@inoc.net> (raw)
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rblayzor.bulk@inoc.net, pgsql-performance@lists.postgresql.org
Subject: Re: partitioning an existing table
In-Reply-To: <D8C4F7BD-FECE-4ABB-9B16-5A764ADBD5DF@inoc.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox