Re: Disallow whole-row index references with virtual generated columns?

From: ZizhuanLiu X-MAN <44973863(at)qq(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Disallow whole-row index references with virtual generated columns?
Date: 2026-06-24 11:54:34
Message-ID: tencent_088D1AAB71089EA52D87166CE2E6DBC7F205@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi everyone,

Thanks a lot for all the patches, tests and insightful discussions so far.

From the current status, PostgreSQL already permits creating indexes with whole-row references.
However, there exists inconsistent handling between such indexes and the query planner during runtime.
As a result, these indexes cannot work as expected, including failures in index scan, index-only scan and
partial predicate matching.

Given this situation, I intend to improve the related logic to provide better index support for
both whole-row references and virtual generated columns.

Therefore, I am sending this proposal: Support virtual generated columns in index expressions and predicates.

regards,
--
ZizhuanLiu (X-MAN)
44973863(at)qq(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-06-24 12:24:35 Re: Proposal: Conflict log history table for Logical Replication
Previous Message ZizhuanLiu X-MAN 2026-06-24 11:41:44 Proposal: Support virtual generated columns in index expressions and predicates