On Mon, Apr 05, 2021 at 06:57:47PM -0400, Tom Lane wrote: > No, I bet it is with "now defines a SQL query". That means there's > something to be stuffed down the pipe. > > I find I can reproduce this pretty reliably on slower machines > here, if you want me to dig into it more carefully.
Now that I think about it, another thing that has changed in this code is the fact that it calls PostgresNode::psql with a result array rather than just the error result, still I don't see how this would have an impact? If you are right, it would be easy to bypass this error with a change in the connect routines to be able to pass down undefined queries rather than filling in a default one. But that does not feel like the root of it. -- Michael
signature.asc
Description: PGP signature
