Message-ID: <cbcefd92-4f43-46ef-8c9f-0c45aa8dca77@gmail.com>
Date: Tue, 17 Mar 2026 11:04:25 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Read-only connection mode for AI workflows.
To: Bruce Momjian <bruce@momjian.us>
Cc: Jack Bonatakis <jack@bonatak.is>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
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>
Content-Language: en-US
From: Andrei Lepikhov <lepihov@gmail.com>
In-Reply-To: <abh1LGa98D2Bpv-n@momjian.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/cbcefd92-4f43-46ef-8c9f-0c45aa8dca77%40gmail.com>
Precedence: bulk

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