From: Laurenz Albe <laurenz.albe@cybertec.at>
To: nik@postgres.ai
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18244: Corruption in indexes involving whole-row expressions
Date: Tue, 12 Dec 2023 23:53:35 +0100
Message-ID: <f577abdc489e75a0b62f0648829d633d75ff8d95.camel@cybertec.at> (raw)
In-Reply-To: <18244-8a7897de2acd5a08@postgresql.org>
References: <18244-8a7897de2acd5a08@postgresql.org>
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...
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, nik@postgres.ai, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18244: Corruption in indexes involving whole-row expressions
In-Reply-To: <f577abdc489e75a0b62f0648829d633d75ff8d95.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox