Subject: Re: overlapping ranges
To: Nick Farrell <nicholas.farrell@gmail.com>
References: <20180120205832.3624.66654@wrigleys.postgresql.org>
 <ee403eb1-ed28-432e-b806-940e7a7acae1@2ndquadrant.com>
 <CANGxkfC16MSumQ5Fhe+y9B36YzHDdUB3OU8DArtJ5Oc2a2mq6A@mail.gmail.com>
Cc: pgsql-docs@lists.postgresql.org,
 PG Doc comments form <noreply@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <b25056a9-4125-11fe-6e52-0026f3853b84@2ndquadrant.com>
Date: Mon, 22 Jan 2018 13:06:39 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: 
 <CANGxkfC16MSumQ5Fhe+y9B36YzHDdUB3OU8DArtJ5Oc2a2mq6A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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