Date: Tue, 17 Mar 2026 09:52:24 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: Jack Bonatakis <jack@bonatak.is>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Read-only connection mode for AI workflows.
Message-ID: <ablcmDxJ2sqdnf_L@momjian.us>
References: 
 <CADsUR0B9bcJQKYHyUMnWcODGzF5+AdeToawULkkTKfrq32Z-8w@mail.gmail.com>
 <64f1c69a-ceff-4b17-8298-58f255d075fc@gmail.com>
 <dde00623-b8e0-421b-a3f7-b149768894ef@app.fastmail.com>
 <fab6a5f3-df9f-4bd7-b2ac-434a17303547@gmail.com>
 <abh1LGa98D2Bpv-n@momjian.us>
 <cbcefd92-4f43-46ef-8c9f-0c45aa8dca77@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cbcefd92-4f43-46ef-8c9f-0c45aa8dca77@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ablcmDxJ2sqdnf_L%40momjian.us>
Precedence: bulk

On Tue, Mar 17, 2026 at 11:04:25AM +0100, Andrei Lepikhov wrote:
> 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?

I think it is a fundamental feature the database should have by default.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.