Re: [Incident report]Backend process crashed when executing 2pc transaction

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: LIANGBO <liangboa(at)suning(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [Incident report]Backend process crashed when executing 2pc transaction
Date: 2019-11-28 05:18:20
Message-ID: CA+HiwqEZswQ-HF+HH3NNpgTS8V+ib81uwjQ8z+4+-3cFg9psJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 28, 2019 at 2:00 PM LIANGBO <liangboa(at)suning(dot)com> wrote:
>
> Hello:
>
> > Have you considered *also* reporting this to Citus developers, because while the crash seems to have occurred in the core 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 bug in 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2019-11-28 05:23:39 Re: dropdb --force
Previous Message LIANGBO 2019-11-28 05:00:47 答复: [Incident report]Backend process crashed when executing 2pc transaction