Re: Issue with partitioning - legitimate insert fails with no partition message

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Sbob <sbob(at)quadratum-braccas(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Issue with partitioning - legitimate insert fails with no partition message
Date: 2022-09-30 15:29:52
Message-ID: 9F1653B6-2CC5-41BD-B63B-14927FF90081@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Sep 30, 2022, at 9:21 AM, Sbob <sbob(at)quadratum-braccas(dot)com> wrote:
>
> 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?

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message yanliang lei 2022-10-05 00:46:18 Does Postgresql support 4KN/512e HDD/SSD?
Previous Message Sbob 2022-09-30 15:21:33 Re: Issue with partitioning - legitimate insert fails with no partition message