| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, nik(at)postgres(dot)ai, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18244: Corruption in indexes involving whole-row expressions |
| Date: | 2023-12-13 04:04:37 |
| Message-ID: | 2528430.1702440277@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aksel Allas | 2023-12-13 06:23:15 | Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION |
| Previous Message | Laurenz Albe | 2023-12-13 03:55:00 | Re: BUG #18244: Corruption in indexes involving whole-row expressions |