Adrian,
On Fri, Aug 1, 2025 at 8:13 PM Adrian Klaver wrote:
>
> On 8/1/25 17:06, Igor Korot wrote:
> > Hi, Laurenz,
>
> >
> > I'm looking at the pg_index table and I see it has:
> >
> > [quote]
> > indisexclusion bool
> >
> > If true, this index supports an exclusion constraint
> > [/quote]
> >
>
On 8/1/25 20:50, Igor Korot wrote:
Adrian,
If I read the docs correctly, this field indicates whether the
WHERE condition is actually present.
Am I right?
No, it refers to:
https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-EXCLUSION
Thx for clarification.
Bu
On 8/1/25 17:06, Igor Korot wrote:
Hi, Laurenz,
I'm looking at the pg_index table and I see it has:
[quote]
indisexclusion bool
If true, this index supports an exclusion constraint
[/quote]
If I read the docs correctly, this field indicates whether the
WHERE condition is actually present.
On Fri, Aug 1, 2025 at 8:06 PM Igor Korot wrote:
>
> If I read the docs correctly, this field indicates whether the
> WHERE condition is actually present.
>
Are you referring to the condition on a partial index? You can get
that using pg_get_expr():
select pg_get_expr(indpred, indrelid) from pg_
Hi, Laurenz,
On Tue, Jul 29, 2025 at 7:07 AM Laurenz Albe wrote:
>
> On Tue, 2025-07-29 at 06:46 -0500, Igor Korot wrote:
> > SELECT
> > t.relname AS table_name,
> > i.relname AS index_name,
> > a.attname AS column_name
> > FROM
> > pg_class t,
> > pg_class i,
> > pg_index
## Siraj G (tosira...@gmail.com):
> I am getting the same error in postgres 12 (sorry that our version upgrade
> sucks).
In all likelyhood, this is a somewhat different situation, as nothing
here points to JIT.
> I see that hash_mem_multiplier is available from version 13. What
> could we do in
