Dean Rasheed writes:
> I spent a little time investigating bug #17759 [1] in more detail.
> Initially, I thought that it had been fixed by 3f7836ff65, but it
> turns out that's not the case.
Thanks for looking closer! I had felt a little unsure about that
too, but hadn't gotten to poking into
I spent a little time investigating bug #17759 [1] in more detail.
Initially, I thought that it had been fixed by 3f7836ff65, but it
turns out that's not the case.
[1]
https://www.postgresql.org/message-id/17759-e76d9bece1b5421c%40postgresql.org
The immediate cause of the bug was that, before
