Request a Demo
Home   >   mailing lists

Re: overlapping ranges - Mailing list pgsql-docs

From Pantelis Theodosiou
Subject Re: overlapping ranges
Date
Msg-id CAE3TBxwXRoko_OD-SSkXSPLPO0RsA_1TP6pXv-Xc0t5BoLzAzw@mail.gmail.com
Whole thread Raw
In response to Re: overlapping ranges  (Nick Farrell <nicholas.farrell@gmail.com>)
List pgsql-docs
Tree view
The CREATE TABLE page has this explanation, about FROM and TO in partitioning declarations:

> When creating a range partition, the lower bound specified with FROM is an inclusive bound, whereas the upper bound specified with TO is an exclusive bound. That is, the values specified in the FROM list are valid values of the corresponding partition key columns for this partition, whereas those in the TO list are not.



On Sat, Jan 20, 2018 at 10:39 PM, Nick Farrell <nicholas.farrell@gmail.com> wrote:
Further down the page, that is contradicted, where there are numeric ranges spaced every hundred, where it says that is disallowed because of the ambiguity at the overlap point. Either way, the documentation is inconsistent.

On 21 Jan. 2018 9:26 am, "Peter Eisentraut" <peter.eisentraut@2ndquadrant.com> wrote:
On 1/20/18 15:58, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/ddl-partitioning.html
> Description:
>
> In the date partitioning example the first and last dates are the first of
> the month, which will cause conflicts. The last date needs to be the final
> day of the same month.

I don't think so, because the upper bound of the range is not included
in the range.

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-docs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: What does "Table rewrite" mean?
Next
From: Peter Eisentraut
Date:
Subject: Re: overlapping ranges