Re: Bug: Whole-row var in indexes corrupts indexes after DDL

On Mon, 31 Aug 2026 at 14:39, Matthias van de Meent <boekewurm(at)gmail(dot)com> wrote:
>
> On Sun, 23 Aug 2026 at 13:26, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> > For the record, an AI-assisted grep over the Hackorum archive puts the
> > virtual generated-column case (a4639d64e2) mentioned in the opening
> > message into a longer sequence: a unique whole-row index becoming
> > inconsistent after DROP COLUMN in 2020 [1], hash_record() indexes after
> > ADD or DROP COLUMN in 2023 [2], the work on whole-row dependencies for
> > DROP COLUMN and ALTER TYPE [3], the virtual generated-column case [4],
> > and rebuilding whole-row CHECK constraints after SET EXPRESSION [5].
> > This seems like good evidence that the general dependency is worth
> > representing, rather than fixing each new manifestation separately.
>
> This evidence is exactly why I started this patch.

v2 had the fixes for the issues you reported that were new and
specific to this patch. v3 is identical to v2 apart from
CompilerWarning fixes.

Kind regards,

Matthias van de Meent
Databricks (https://www.databricks.com)