public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrei Lepikhov <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Jack Bonatakis <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: Read-only connection mode for AI workflows.
Date: Tue, 17 Mar 2026 11:04:25 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CADsUR0B9bcJQKYHyUMnWcODGzF5+AdeToawULkkTKfrq32Z-8w@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
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
view thread (20+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Read-only connection mode for AI workflows.
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox