MIME-Version: 1.0
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>
 <7f6e0ff9-05e9-4664-9c71-d9dd744362b9@gmail.com>
 <CAFj8pRC5jqo3DwOfXCyRh8hHMr8xWk3CTHV_XWsQPZ1Y7QV6PQ@mail.gmail.com>
 <42ca6abe-774b-404b-b4a2-27d8792b23fb@gmail.com>
In-Reply-To: <42ca6abe-774b-404b-b4a2-27d8792b23fb@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Thu, 19 Mar 2026 10:49:24 +0100
Message-ID: 
 <CAFj8pRC43My_CwC8e4S+b3R6XNviK75A=q-_utoQTwABegxx1Q@mail.gmail.com>
Subject: Re: Read-only connection mode for AI workflows.
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>
Content-Type: multipart/alternative; boundary="000000000000f96880064d5d7dcf"
Archived-At: 
 <https://www.postgresql.org/message-id/CAFj8pRC43My_CwC8e4S%2Bb3R6XNviK75A%3Dq-_utoQTwABegxx1Q%40mail.gmail.com>
Precedence: bulk

--000000000000f96880064d5d7dcf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi

=C4=8Dt 19. 3. 2026 v 9:40 odes=C3=ADlatel Andrei Lepikhov <lepihov@gmail.c=
om> 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=E2=80=99t overcome this rule.
>

I am sorry. I missed so you used standard_ExecutorStart

Regards

Pavel


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

--000000000000f96880064d5d7dcf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote gmail_quote_con=
tainer"><div dir=3D"ltr" class=3D"gmail_attr">=C4=8Dt 19. 3. 2026 v=C2=A09:=
40 odes=C3=ADlatel Andrei Lepikhov &lt;<a href=3D"mailto:lepihov@gmail.com"=
>lepihov@gmail.com</a>&gt; napsal:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">On 19/3/26 08:53, Pavel Stehule wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0We could improve it by restricting manual calls to =
specific utility<br>
&gt;=C2=A0 =C2=A0 =C2=A0operations, such as VACUUM or REINDEX. However, we =
would need some<br>
&gt;=C2=A0 =C2=A0 =C2=A0specifications first.<br>
&gt; <br>
&gt; <br>
&gt; It doesn&#39;t=C2=A0cover=C2=A0 possibility to set GUC by set_config f=
unction<br>
<br>
Can you explain it? I added a test for the set_config() call.<br>
This extension is so tiny because it exploits the rule: no ro -&gt; rw <br>
switch after a snapshot has been taken (but rw -&gt; ro is possible). The <=
br>
set_config can=E2=80=99t overcome this rule.<br></blockquote><div><br></div=
><div>I am sorry. I missed so you used=C2=A0standard_ExecutorStart</div><di=
v><br></div><div>Regards</div><div><br></div><div>Pavel</div><div>=C2=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- <br>
regards, Andrei Lepikhov,<br>
pgEdge<br>
</blockquote></div></div>

--000000000000f96880064d5d7dcf--