On Thu, Nov 28, 2019 at 2:00 PM LIANGBO <liangboa@suning.com> wrote:
>
> Hello:
>
> > Have you considered *also* reporting this to Citus developers, because while the crash seems to have occurred in
thecore PostgreSQL code they may have a better chance reproducing this if at all.
>
> I've sent this issue to the citus community, and then received the reply with "Just a note that this appears to be a
bugin Postgres 2PC code.".
> https://github.com/citusdata/citus/issues/3228
Interesting. Still, I think you'd be in better position than anyone
else to come up with reproduction steps for vanilla PostgreSQL by
analyzing the stack trace if and when the crash next occurs (or using
the existing core dump). It's hard to tell by only guessing what may
have gone wrong when there is external code involved, especially
something like Citus that hooks into many points within vanilla
PostgreSQL.
Thanks,
Amit
