| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com> |
| Cc: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Jack Bonatakis <jack(at)bonatak(dot)is>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Read-only connection mode for AI workflows. |
| Date: | 2026-03-19 21:59:07 |
| Message-ID: | CAOYmi+=wgTAyECGXtY3K-R8_tyz43zqVxPR6ueB+Cnso0s9c_A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 19, 2026 at 12:39 PM SATYANARAYANA NARLAPURAM
<satyanarlapuram(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-03-19 22:02:28 | Re: pg_plan_advice |
| Previous Message | Robert Haas | 2026-03-19 21:33:37 | Re: pg_plan_advice |