Re: BUG #18244: Corruption in indexes involving whole-row expressions

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: 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-12 22:53:35
Message-ID: f577abdc489e75a0b62f0648829d633d75ff8d95.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 2023-12-12 at 19:28 +0000, PG Bug reporting form wrote:
> nik=# create index on t1 (hash_record(t1));
>
> Such an index can easily be corrupted, e.g.:
>
> nik=# alter table t1 add column yo int default -1;
>
> Proposal: prohibit the use of whole-row expression – as it is already done
> for generated columns and produce a similar error ("cannot use whole-row
> variable in column generation expression")

I reported that bug before:
https://www.postgresql.org/message-id/flat/e48a5d9a2d3d72985d61ee254314f5f5f5444a55.camel%40cybertec.at

I think that your proposal is good, it seems that nobody cared enough
to implement it. If we forbid that, one thing to consider is pg_upgrade:
it needs a new check.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro Horiguchi 2023-12-13 00:46:10 Re: BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
Previous Message PG Bug reporting form 2023-12-12 19:28:29 BUG #18244: Corruption in indexes involving whole-row expressions