-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Hi,
I wonder why you use your own control [1] over the existing XactReadOnly machinery? It seems to me that it would be enough if your GUC just changed and restored this value in the backend on Executor Start (potentially, during planning/parsing) - the standard ExecCheckXactReadOnly() should prevent DML/DDL executions ...
Also, I think for the replication apply workers, this restriction might be implemented through a SMGR hook somehow.
[1]
Line 454 in ea52059
| ereport(ERROR, (errmsg("pg_readonly: pgro_exec: invalid statement because cluster is read-only"))); |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels