| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | Jack Bonatakis <jack(at)bonatak(dot)is>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(dot)momjian(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Read-only connection mode for AI workflows. |
| Date: | 2026-03-19 09:49:24 |
| Message-ID: | CAFj8pRC43My_CwC8e4S+b3R6XNviK75A=q-_utoQTwABegxx1Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
čt 19. 3. 2026 v 9:40 odesílatel Andrei Lepikhov <lepihov(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Burd | 2026-03-19 09:55:49 | Re: another autovacuum scheduling thread |
| Previous Message | Peter Eisentraut | 2026-03-19 09:48:36 | Re: Feature freeze timezone change request |