pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christophe Pettus <xof@thebuild.com>
To: allen.sutton@valocityglobal.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17525: Range partition by date won't allow the use of a date that is the upper bound
Date: Tue, 21 Jun 2022 16:33:38 -0700
Message-ID: <7D0BE81B-40BA-4901-973E-70FFC4C01034@thebuild.com> (raw)
In-Reply-To: <17525-ffa3a5fe34f8c6f4@postgresql.org>
References: <17525-ffa3a5fe34f8c6f4@postgresql.org>



> 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).




view thread (3+ messages)

Message-ID: <7D0BE81B-40BA-4901-973E-70FFC4C01034@thebuild.com>
Permalink:  ../7D0BE81B-40BA-4901-973E-70FFC4C01034@thebuild.com/
Also on:    postgresql.org/message-id/7D0BE81B-40BA-4901-973E-70FFC4C01034@thebuild.com

 · 

reply

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-bugs@postgresql.org
  Cc: xof@thebuild.com, allen.sutton@valocityglobal.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17525: Range partition by date won't allow the use of a date that is the upper bound
  In-Reply-To: <7D0BE81B-40BA-4901-973E-70FFC4C01034@thebuild.com>

* 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