From: Laurenz Albe <laurenz.albe@cybertec.at>
To: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Technical guidance for a large partition table
Date: Mon, 10 May 2021 07:45:47 +0200
Message-ID: <dc39fd4d13f80336f9080bf290f4ca7c90c33982.camel@cybertec.at> (raw)
In-Reply-To: <EF56C0B6-A15B-4784-817F-60627BE46B96@gmail.com>
References: <EF56C0B6-A15B-4784-817F-60627BE46B96@gmail.com>
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.
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-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, jayknowsunix@gmail.com
Subject: Re: Technical guidance for a large partition table
In-Reply-To: <dc39fd4d13f80336f9080bf290f4ca7c90c33982.camel@cybertec.at>
* 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