Re: BUG #18244: Corruption in indexes involving whole-row expressions - Mailing list pgsql-bugs

From Laurenz Albe
Subject Re: BUG #18244: Corruption in indexes involving whole-row expressions
Date
Msg-id ce4165ffeac66281faa05cd9fc5ceabebe210af0.camel@cybertec.at
Whole thread Raw
In response to Re: BUG #18244: Corruption in indexes involving whole-row expressions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #18244: Corruption in indexes involving whole-row expressions
List pgsql-bugs
On Tue, 2023-12-12 at 23:04 -0500, Tom Lane wrote:
> Laurenz Albe <laurenz.albe@cybertec.at> writes:
> > Should we forbid composite types in index declarations?  Sounds posssible,
> > but very restrictive.
>
> That would make a lot of people very sad, I fear.
>
> I think a minimum answer could be to document that you might need to
> REINDEX such indexes after a change in the composite type.  We could
> perhaps try to be more proactive, say by marking such indexes invalid.
> I think though that that would have deadlock problems as well as race
> conditions.  Perhaps best to leave it at "reindex when necessary",
> especially in view of the tiny number of reports to date.

I agree.  How about the attached documentation patch?

Yours,
Laurenz Albe

Attachment

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18248: Expression is always zero
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: about psql copy ,we would like to seek help,Thanks.