On Thu, Feb 14, 2019 at 2:27 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So my bet is that your problem was fixed by some other commit between
> 10.3 and 10.6. Maybe the predecessor one, b767b3f2e; but hard to say
> without more investigation than seems warranted, if the bug's gone.
I wonder if jfinzel is in a position to do a git-bisect. That might be
interesting.
--
Peter Geoghegan