Re: Read-only connection mode for AI workflows.

Pavel Stehule <pavel.stehule@gmail.com>

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

To: Andrei Lepikhov <lepihov@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-19T09:49:24Z

Lists: pgsql-hackers

Hi

čt 19. 3. 2026 v 9:40 odesílatel Andrei Lepikhov <lepihov@gmail.com> napsal:

> 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.
>

I am sorry. I missed so you used standard_ExecutorStart

Regards

Pavel


>
> --
> regards, Andrei Lepikhov,
> pgEdge
>