is there any specific use of setting transaction_read_only GUC externally? - Mailing list pgsql-hackers

From Srinath Reddy Sadipiralla
Subject is there any specific use of setting transaction_read_only GUC externally?
Date
Msg-id CAFC+b6odXTf4ZUR8ZmSNjq9LL1OwBb3qzsru432ds4Nh0s50Vg@mail.gmail.com
Whole thread Raw
List 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/

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: 024_add_drop_pub.pl might fail due to deadlock
Next
From: Fabrice Chapuis
Date:
Subject: Re: Postgres keep alive configuration