On 1/20/18 17:39, Nick Farrell 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.
That talks about the old way of doing partitioning, which works
differently
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
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.eisentr...@2ndquadran
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,
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 fi
