Re: Read-only connection mode for AI workflows.

Andrei Lepikhov <lepihov@gmail.com>

From: Andrei Lepikhov <lepihov@gmail.com>

To: Pavel Stehule <pavel.stehule@gmail.com>

Cc: Jack Bonatakis <jack@bonatak.is>, pgsql-hackers <pgsql-hackers@postgresql.org>, Bruce Momjian <bruce.momjian@enterprisedb.com>, Andres Freund <andres@anarazel.de>

Date: 2026-03-19T08:40:15Z

Lists: pgsql-hackers

On 19/3/26 08:53, Pavel Stehule wrote:
>     We could improve it by restricting manual calls to specific utility
>     operations, such as VACUUM or REINDEX. However, we would need some
>     specifications first.
> 
> 
> It doesn't cover  possibility to set GUC by set_config function

Can you explain it? I added a test for the set_config() call.
This extension is so tiny because it exploits the rule: no ro -> rw 
switch after a snapshot has been taken (but rw -> ro is possible). The 
set_config can’t overcome this rule.

-- 
regards, Andrei Lepikhov,
pgEdge