| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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-17 10:04:25 |
| Message-ID: | cbcefd92-4f43-46ef-8c9f-0c45aa8dca77@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/3/26 22:25, Bruce Momjian wrote:
> On Mon, Mar 16, 2026 at 10:01:22PM +0100, Andrei Lepikhov wrote:
>>> I do think the underlying problem of safely exposing databases to
>>> automated agents is becoming increasingly common, so it seems like a
>>> useful area to explore.
>
> I agree the need a read-only sessions is going to get more urgent with
> MCP. Why doesn't the community code have a read-only session option
> that can't be changed?
The pg_readonly project aims to answer this question: if it is easy and
cheap to implement as an extension, why do we need to touch the core?
--
regards, Andrei Lepikhov,
pgEdge
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2026-03-17 10:23:26 | Re: meson: Make test output much more useful on failure (both in CI and locally) |
| Previous Message | Ashutosh Bapat | 2026-03-17 09:53:50 | Re: SQL Property Graph Queries (SQL/PGQ) |