Re: concurrent re-partitioning of declarative partitioned tables - Mailing list pgsql-general

From Nick Cleaton
Subject Re: concurrent re-partitioning of declarative partitioned tables
Date
Msg-id CAFgz3kv1RiYcnvuCy4K_dBQrRJoNp79jf=fAeb_+eGcjbi8zjA@mail.gmail.com
Whole thread Raw
In response to Re: concurrent re-partitioning of declarative partitioned tables  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On Wed, 2 Dec 2020 at 16:07, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Mon, Nov 30, 2020 at 8:36 AM Nick Cleaton <nick@cleaton.net> wrote:
I want to set up a large table on postgresql 12.4, using declarative partitioning to partition by record creation date. I'd like to have recent records in small partitions but old records in a few larger partitions, so I want merges. The merges should be concurrent, in the sense that they lock out readers or writers only for very short intervals if at all.

Once a date has passed is the table for that date effectively read-only?

No, old records get updated from time to time, although updates are much less common than for recent records.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: concurrent re-partitioning of declarative partitioned tables
Next
From: Nick Cleaton
Date:
Subject: Re: concurrent re-partitioning of declarative partitioned tables