Re: BUG #17525: Range partition by date won't allow the use of a date that is the upper bound - Mailing list pgsql-bugs

From Christophe Pettus
Subject Re: BUG #17525: Range partition by date won't allow the use of a date that is the upper bound
Date
Msg-id 7D0BE81B-40BA-4901-973E-70FFC4C01034@thebuild.com
Whole thread Raw
In response to BUG #17525: Range partition by date won't allow the use of a date that is the upper bound  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs

> On Jun 21, 2022, at 16:11, PG Bug reporting form <noreply@postgresql.org> wrote:
> e.g. CREATE TABLE avm.avm_history_201704 PARTITION OF avm.avm_history_part
>    FOR VALUES FROM ('2017-04-01') TO ('2017-04-30');

The upper bound on a range partition is exclusive: The partition is defined as from 2017-04-01 up to, but not including
2017-04-30. If you want full-month partitions, you probably want the upper bound to be 2017-05-01 (in this example). 


pgsql-bugs by date:

Previous
From: Allen Sutton
Date:
Subject: RE: BUG #17525: Range partition by date won't allow the use of a date that is the upper bound
Next
From: PG Bug reporting form
Date:
Subject: BUG #17526: PG_DUMP is not outputting "CREATE SCHEMA" statements when an extension is assigned to a schema