MIME-Version: 1.0
In-Reply-To: 
 <CANGxkfC16MSumQ5Fhe+y9B36YzHDdUB3OU8DArtJ5Oc2a2mq6A@mail.gmail.com>
References: <20180120205832.3624.66654@wrigleys.postgresql.org>
 <ee403eb1-ed28-432e-b806-940e7a7acae1@2ndquadrant.com>
 <CANGxkfC16MSumQ5Fhe+y9B36YzHDdUB3OU8DArtJ5Oc2a2mq6A@mail.gmail.com>
From: Pantelis Theodosiou <ypercube@gmail.com>
Date: Mon, 22 Jan 2018 09:31:48 +0000
Message-ID: 
 <CAE3TBxwXRoko_OD-SSkXSPLPO0RsA_1TP6pXv-Xc0t5BoLzAzw@mail.gmail.com>
Subject: Re: overlapping ranges
To: Nick Farrell <nicholas.farrell@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
 pgsql-docs@lists.postgresql.org,
	PG Doc comments form <noreply@postgresql.org>
Content-Type: multipart/alternative; boundary="001a113f76b8a37e5405635a1a77"
Precedence: bulk

--001a113f76b8a37e5405635a1a77
Content-Type: text/plain; charset="UTF-8"

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

--001a113f76b8a37e5405635a1a77
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The CREATE TABLE page has this explanation, about FROM and=
 TO in partitioning declarations:<br><br>&gt; When creating a range partiti=
on, the lower bound
          specified with <code class=3D"gmail-literal">FROM</code> is an
          inclusive bound, whereas the upper bound specified with
          <code class=3D"gmail-literal">TO</code> is an exclusive bound.
          That is, the values specified in the <code class=3D"gmail-literal=
">FROM</code> list are valid values of the
          corresponding partition key columns for this partition,
          whereas those in the <code class=3D"gmail-literal">TO</code> list
          are not.<br><br><br><div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Sat, Jan 20, 2018 at 10:39 PM, Nick Farrell <span dir=
=3D"ltr">&lt;<a href=3D"mailto:nicholas.farrell@gmail.com" target=3D"_blank=
">nicholas.farrell@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"auto">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.</div><div class=3D"gmail-HOE=
nZb"><div class=3D"gmail-h5"><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On 21 Jan. 2018 9:26 am, &quot;Peter Eisentraut&quot; &lt;<a hr=
ef=3D"mailto:peter.eisentraut@2ndquadrant.com" target=3D"_blank">peter.eise=
ntraut@2ndquadrant.<wbr>com</a>&gt; wrote:<br type=3D"attribution"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">On 1/20/18 15:58, PG Doc comments=
 form wrote:<br>
&gt; The following documentation comment has been logged on the website:<br=
>
&gt;<br>
&gt; Page: <a href=3D"https://www.postgresql.org/docs/10/static/ddl-partiti=
oning.html" rel=3D"noreferrer" target=3D"_blank">https://www.postgresql.org=
/doc<wbr>s/10/static/ddl-partitioning.<wbr>html</a><br>
&gt; Description:<br>
&gt;<br>
&gt; In the date partitioning example the first and last dates are the firs=
t of<br>
&gt; the month, which will cause conflicts. The last date needs to be the f=
inal<br>
&gt; day of the same month.<br>
<br>
I don&#39;t think so, because the upper bound of the range is not included<=
br>
in the range.<br>
<br>
--<br>
Peter Eisentraut=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D=
"http://www.2ndQuadrant.com/" rel=3D"noreferrer" target=3D"_blank">http://w=
ww.2ndQuadrant.com/</a><br>
PostgreSQL Development, 24x7 Support, Remote DBA, Training &amp; Services<b=
r>
</blockquote></div></div>
</div></div></blockquote></div><br></div></div></div>

--001a113f76b8a37e5405635a1a77--