| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | John Scalia <jayknowsunix(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Technical guidance for a large partition table |
| Date: | 2021-05-10 05:45:47 |
| Message-ID: | dc39fd4d13f80336f9080bf290f4ca7c90c33982.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sun, 2021-05-09 at 19:18 -0400, John Scalia wrote:
> I have a dev team requesting that I partition 3 very large tables with more 2 billion rows each.
> I’ve already got the partition key decided for each with a script which will create a copy of
> original with the partition declaration, along with the partition child tables.
> [...]
> FYI, this is production instance that is regularly updated by field technicians.
> Quite literally, I cannot perform two sequential select count(*) from any of these tables
> which will return the same row counts.
From v13 on, you should be able to use logical replication to partition a table with
little downtime.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rammohan ganapavarapu | 2021-05-13 17:09:12 | Changing wal_level |
| Previous Message | Keith | 2021-05-10 01:14:33 | Re: Technical guidance for a large partition table |