is there any specific use of setting transaction_read_only GUC externally?

From: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: is there any specific use of setting transaction_read_only GUC externally?
Date: 2025-07-23 12:40:00
Message-ID: CAFC+b6odXTf4ZUR8ZmSNjq9LL1OwBb3qzsru432ds4Nh0s50Vg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
$SUBJECT,because anyway after the next transaction starts XactReadOnly is
going to change depending on either RecoveryInProgress()
or DefaultXactReadOnly GUC ,so if there's no specific use to
set transaction_read_only GUC can we change its GucContext from PGC_USERSET
to PGC_INTERNAL and remove check_transaction_read_only api which makes it
clear that we can't set it externally and only we can use SHOW on it,
thoughts?

--
Thanks,
Srinath Reddy Sadipiralla
EDB: https://www.enterprisedb.com/

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrice Chapuis 2025-07-23 12:40:04 Re: Postgres keep alive configuration
Previous Message Ajin Cherian 2025-07-23 11:58:39 Re: 024_add_drop_pub.pl might fail due to deadlock