Re: Exclusion constraints on partitioned tables

From: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Exclusion constraints on partitioned tables
Date: 2023-07-10 15:06:31
Message-ID: CA+renyVP0MPh-7cK=wSLoStHPFQX3LMPiYitvOwJKfqbS7ETDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 10, 2023 at 7:05 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> I'm not sure what value we would get from testing this with btree_gist,
> but if we wanted to do that, then adding a new test file to the
> btree_gist sql/ directory would seem reasonable to me.
>
> (I would make the test a little bit bigger than you had shown, like
> insert a few values.)
>
> If you want to do that, please send another patch. Otherwise, I'm ok to
> commit this one.

I can get you a patch tonight or tomorrow. I think it's worth it since
btree_gist uses different strategy numbers than ordinary gist.

Thanks!
Paul

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-07-10 15:09:44 Re: PATCH: Using BRIN indexes for sorted output
Previous Message Tom Lane 2023-07-10 15:04:48 Re: Add more sanity checks around callers of changeDependencyFor()