On Thu, Jan 16, 2020 at 10:46:55AM -0800, Christophe Pettus wrote:
> We've been encountering the same bug; here's a stack trace from the
> crashed process:
>
> [stack trace]
I cannot say if Pendekar's bug is the same issue, but yours looks very
familiar to that:
https://www.postgresql.org/message-id/16129-a0c0f48e71741e5f@postgresql.org
And this has already been fixed, in time for 12.2.
--
Michael
