On Mon, Oct 23, 2017 at 9:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This is probably enough info for us to identify the exact cause. But
> I don't have time to look right this minute, and am not the hacker most
> familiar with the GIN infrastructure anyway. Anyone want to look for
> the bug?
I don't know very much about GIN, but this does look interesting. I'll
try to get to it later in the week; I have meetings over the next
couple of days.
--
Peter Geoghegan