Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Feike Steenbergen <feikesteenbergen(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Date: 2025-06-25 08:11:28
Message-ID: 4649a351-3500-45af-90ab-c3dfb16f1e65@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.06.25 15:13, Peter Eisentraut wrote:
> Your CheckAttributeType() change is conditional on TYPTYPE_BASE, but if
> you remove that and check it for all types, then you get the right error
> in both cases.
>
> I have attached a patch that is similar to yours but with that change.
> I've also written the test cases a bit differently, but it also covers
> everything now.
>
> (The two patches should be squashed.  I'm just keeping them separate to
> show what is changed.)

This has been committed thus. This should close this topic.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-06-25 08:15:31 Re: Remove HeapTupleheaderSetXmin{Committed,Invalid} functions
Previous Message Jim Jones 2025-06-25 08:01:40 display hot standby state in psql prompt