Re: Read-only connection mode for AI workflows. - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: Read-only connection mode for AI workflows.
Date
Msg-id 42ca6abe-774b-404b-b4a2-27d8792b23fb@gmail.com
Whole thread Raw
In response to Re: Read-only connection mode for AI workflows.  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Read-only connection mode for AI workflows.
List 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



pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Release postmaster working memory context in slotsync worker
Next
From: JoongHyuk Shin
Date:
Subject: Re: pg_dump: fix NOT NULL constraint name comparison using makeObjectName