You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Clean up handling of XactReadOnly and RecoveryInProgress checks.
Add some checks that seem logically necessary, in particular let's makereal sure that HS slave sessions cannot create temp tables. (If they didthey would think that temp tables belonging to the master's session withthe same BackendId were theirs. We *must* not allow myTempNamespace tobecome set in a slave session.)Change setval() and nextval() so that they are only allowed on temp sequencesin a read-only transaction. This seems consistent with what we allow fortable modifications in read-only transactions. Since an HS slave can't have atemp sequence, this also provides a nicer cure for the setval PANIC reportedby Erik Rijkers.Make the error messages more uniform, and have them mention the specificcommand being complained of. This seems worth the trifling amount of extracode, since people are likely to see such messages a lot more than before.