Markus Winand <markus.win...@winand.at> writes: > What I meant is that it was still working on > 4ac0f450b698442c3273ddfe8eed0e1a7e56645f, but not on the next > (3f50b82639637c9908afa2087de7588450aa866b).
Yeah, silly oversight in that patch. Will push a fix shortly.
regards, tom lane
