Hi,
On Wed, Jan 19, 2022 at 09:30:11AM +0100, Peter Eisentraut wrote:
>
> To use exclusion constraints in practice, you often need to install the
> btree_gist extension, so that you can combine for example a range type check
> and normal scalar key columns into one constraint.
>
> [...]
>
> There
> Thoughts?
I think it'd be really nice to do this without btree_gist.
I imagine something like this:
CREATE INDEX ON tbl USING gist (
range_col,
int_col USING btree
)
I think this would make the index access methods interface more
useful. Index access method developers wouldn't need t
Andreas Karlsson writes:
> On 1/19/22 09:30, Peter Eisentraut wrote:
>> I don't have a lot of experience with this module, so I don't know if
>> there are any lingering concerns about whether it is mature enough as a
>> built-in feature.
> While it I like the idea on a conceptual level I worry
On 1/19/22 09:30, Peter Eisentraut wrote:
So, first of all, would people agree with this course of action?
I don't have a lot of experience with this module, so I don't know if
there are any lingering concerns about whether it is mature enough as a
built-in feature.
While it I like the idea
ilt-in SQL feature that relied
on an extension to work at all. So I think the way forward would be to
move btree_gist into core, and I'm starting this new thread here to give
this topic a bit more attention.
So, first of all, would people agree with this course of action?
I don't have
