Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: Issue with partitioning - legitimate insert fails with no
 partition message
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <42b71a74-1439-4bfa-5a3f-727e712c2ca0@quadratum-braccas.com>
Date: Fri, 30 Sep 2022 09:29:52 -0600
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F1653B6-2CC5-41BD-B63B-14927FF90081@elevated-dev.com>
References: <2121b49f-52fb-ab79-3ea1-c398d7a8656f@quadratum-braccas.com>
 <42b71a74-1439-4bfa-5a3f-727e712c2ca0@quadratum-braccas.com>
To: Sbob <sbob@quadratum-braccas.com>
Archived-At: 
 <https://www.postgresql.org/message-id/9F1653B6-2CC5-41BD-B63B-14927FF90081%40elevated-dev.com>
Precedence: bulk

> On Sep 30, 2022, at 9:21 AM, Sbob <sbob@quadratum-braccas.com> wrote:
>=20
> It seems that the range for partitions is inclusive of the starting =
value and exclusive of the ending value, maybe this is documented and I =
missed it?

Yes, it is. (and "to" is not "through")

The explanation is: think of a floating-point value, if it included the =
end value would you use XXX.999, or XXX.9999, or XXX.99999... Same =
argument applies to timestamps--even though they are stored as 64-bit =
integers, how would you figure out the value that is 1 bit less than =
your end date?