From: | Nick Cleaton <nick(at)cleaton(dot)net> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: concurrent re-partitioning of declarative partitioned tables |
Date: | 2020-12-02 16:22:05 |
Message-ID: | CAFgz3kv1RiYcnvuCy4K_dBQrRJoNp79jf=fAeb_+eGcjbi8zjA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2 Dec 2020 at 16:07, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Mon, Nov 30, 2020 at 8:36 AM Nick Cleaton <nick(at)cleaton(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Cleaton | 2020-12-02 16:53:38 | Re: concurrent re-partitioning of declarative partitioned tables |
Previous Message | David G. Johnston | 2020-12-02 16:07:45 | Re: concurrent re-partitioning of declarative partitioned tables |