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

From: Feike Steenbergen <feikesteenbergen(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(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-05-29 18:01:27
Message-ID: CAK_s-G1tePk2GyjQBmb3T9MnwMuiyOcjpmDprKAdmm04qmGOKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 29 May 2025 at 15:43, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> that would also imply,
> for example, that there's no way to run a pg_dump without letting any
> user on the system obtain superuser privileges.

I checked, pg_dump seems safe, it doesn't extract the values, even when
using --column-inserts.

pg_restore may have issues though, as it will run these functions
for GENERATED STORED columns?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-05-29 18:15:22 Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Previous Message Tom Lane 2025-05-29 17:02:39 Re: Fixing memory leaks in postgres_fdw