public inbox for [email protected]
help / color / mirror / Atom feedoverlapping ranges
5+ messages / 4 participants
[nested] [flat]
* overlapping ranges
@ 2018-01-20 20:58 PG Doc comments form <[email protected]>
2018-01-20 22:26 ` Re: overlapping ranges Peter Eisentraut <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: PG Doc comments form @ 2018-01-20 20:58 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: overlapping ranges
2018-01-20 20:58 overlapping ranges PG Doc comments form <[email protected]>
@ 2018-01-20 22:26 ` Peter Eisentraut <[email protected]>
2018-01-20 22:39 ` Re: overlapping ranges Nick Farrell <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 2018-01-20 22:26 UTC (permalink / raw)
To: [email protected]; [email protected]; PG Doc comments form <[email protected]>
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: overlapping ranges
2018-01-20 20:58 overlapping ranges PG Doc comments form <[email protected]>
2018-01-20 22:26 ` Re: overlapping ranges Peter Eisentraut <[email protected]>
@ 2018-01-20 22:39 ` Nick Farrell <[email protected]>
2018-01-22 09:31 ` Re: overlapping ranges Pantelis Theodosiou <[email protected]>
2018-01-22 18:06 ` Re: overlapping ranges Peter Eisentraut <[email protected]>
0 siblings, 2 replies; 5+ messages in thread
From: Nick Farrell @ 2018-01-20 22:39 UTC (permalink / raw)
To: Peter Eisentraut <[email protected]>; +Cc: [email protected]; PG Doc comments form <[email protected]>
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" <
[email protected]> 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
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: overlapping ranges
2018-01-20 20:58 overlapping ranges PG Doc comments form <[email protected]>
2018-01-20 22:26 ` Re: overlapping ranges Peter Eisentraut <[email protected]>
2018-01-20 22:39 ` Re: overlapping ranges Nick Farrell <[email protected]>
@ 2018-01-22 09:31 ` Pantelis Theodosiou <[email protected]>
1 sibling, 0 replies; 5+ messages in thread
From: Pantelis Theodosiou @ 2018-01-22 09:31 UTC (permalink / raw)
To: Nick Farrell <[email protected]>; +Cc: Peter Eisentraut <[email protected]>; [email protected]; PG Doc comments form <[email protected]>
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 <[email protected]>
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
>>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: overlapping ranges
2018-01-20 20:58 overlapping ranges PG Doc comments form <[email protected]>
2018-01-20 22:26 ` Re: overlapping ranges Peter Eisentraut <[email protected]>
2018-01-20 22:39 ` Re: overlapping ranges Nick Farrell <[email protected]>
@ 2018-01-22 18:06 ` Peter Eisentraut <[email protected]>
1 sibling, 0 replies; 5+ messages in thread
From: Peter Eisentraut @ 2018-01-22 18:06 UTC (permalink / raw)
To: Nick Farrell <[email protected]>; +Cc: [email protected]; PG Doc comments form <[email protected]>
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 in this respect.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2018-01-22 18:06 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-01-20 20:58 overlapping ranges PG Doc comments form <[email protected]>
2018-01-20 22:26 ` Peter Eisentraut <[email protected]>
2018-01-20 22:39 ` Nick Farrell <[email protected]>
2018-01-22 09:31 ` Pantelis Theodosiou <[email protected]>
2018-01-22 18:06 ` Peter Eisentraut <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox