Re: Overlapping values (?) in multi-column partitioned tables

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Christophe Pettus <xof(at)thebuild(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Overlapping values (?) in multi-column partitioned tables
Date: 2024-09-10 23:02:11
Message-ID: CAApHDvpfrn-ddUYVXSOV1BvoF8npqyZxZts7Gsg6nNR=FJg4Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 11 Sept 2024 at 10:57, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> You should specify the upper bound as ('2023-12-31 23:59:59.999999', MAXVALUE).

Or maybe do multi-level partitioning.

(it seems strange to always have MINVALUE and MAXVALUE as the range.
I'm guessing that was just an example.)

David

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2024-09-10 23:05:47 Re: Overlapping values (?) in multi-column partitioned tables
Previous Message Laurenz Albe 2024-09-10 22:57:38 Re: Overlapping values (?) in multi-column partitioned tables