It looks like updating pg_constraint isn't an option for AWS RDS due to the
way AWS doesn't give you superuser access.
Thanks a lot for the suggestion anyway.
On Fri, 15 Nov 2024 at 15:28, Torsten Förtsch
wrote:
> On Fri, Nov 15, 2024 at 9:38 AM Philip Couling wrote:
>
>
t;= DATE '2008-03-01'
Hope that clarifies it.
On Wed, 20 Nov 2024 at 09:45, jian he wrote:
> On Fri, Nov 15, 2024 at 4:38 PM Philip Couling wrote:
> >
> > Is there a solid reason why adding a check constraint does not use
> existing indexes for validation.
>
constraint, so there is a difference there. But
besides that, it’s very clear that Postgres does not make use of indexes
while validating constraints. I suspect it doesn’t involve the query
planner at all.
On Fri, 15 Nov 2024 at 15:28, Torsten Förtsch
wrote:
> On Fri, Nov 15, 2024 at 9:38 AM Phi
Is there a solid reason why adding a check constraint does not use existing
indexes for validation.
We are currently looking at partitioning a multi TB table leaving all
existing data in place and simply attaching it as a partition to a new
table. To prevent locking, we are trying to add an INVALI
