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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, 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-05 19:15:53
Message-ID: CA+TgmoZ3mePXUTHAa7RgbFfAe2Do+GphDrVe45xEQ=3rA9TPCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 5, 2025 at 11:19 AM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> I think it will work.
> because we already require the generated column expression to be
> immutable functions.
>
> The above functions you mentioned are all not immutable.

Hmm. I guess I have no evidence that we have built-in immutable
functions that would cause a problem here. I still think it's a bad
direction to go.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-06-05 19:44:11 Re: Some questions about gin index
Previous Message Alexander Lakhin 2025-06-05 19:00:00 Re: Non-reproducible AIO failure