On 1/3/26 7:03 PM, Tom Lane wrote:
Andreas Karlsson <[email protected]> writes:
A potential third option would be to take your solution but to add a
HINT about that it needs to run as a top-level statement outside any
transactions, but I kinda liked how simple the original patch was.
Yeah, I like just adding "or procedure" and calling it good.
I do not think we need a regression test, either ...
Yeah, let's keep it simple.
Poking around, I also found this:
src/backend/commands/wait.c: errdetail("WAIT FOR cannot
be executed from a function or a procedure or within a transaction with an isolation
level higher than READ COMMITTED."));
which is also not great grammar. What do you think of "WAIT FOR
cannot be executed from a function or procedure, nor within a
transaction with an isolation level higher than READ COMMITTED." ?
Much better!
Andreas
