Horton
Menu

Re: Read-only connection mode for AI workflows.

Jacob Champion <jacob.champion@enterprisedb.com>

View thread
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Cc: Andrei Lepikhov <lepihov@gmail.com>, Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter@eisentraut.org>, Bruce Momjian <bruce@momjian.us>, Jack Bonatakis <jack@bonatak.is>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2026-03-19T21:59:07Z
Lists: pgsql-hackers 
On Thu, Mar 19, 2026 at 12:39 PM SATYANARAYANA NARLAPURAM
<satyanarlapuram@gmail.com> wrote:
> +1 to scenarios Andres' mentioned. Additional cases where a cluster‑wide setting is helpful include disk‑full events and policy enforcement, where write access is revoked but read access is preserved for data exfiltration.

I've additionally wanted this during orchestrated pg_upgrade
scenarios, to apply to the old cluster.

--Jacob