From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | ocean_li_996(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder() |
Date: | 2023-08-17 03:24:29 |
Message-ID: | CAA4eK1JHPR42FqbNb9239oNQYSEofhGrUASxC9RXttB0tdX0_A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Aug 14, 2023 at 11:06 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> Using of NInitialRunningXacts and InitialRunningXacts are clear. Currently,
> the core, as far as i know, maybe caused by this way: an ERROR raised when
> calling *pg_logical_slot_get_changes_guts* function. The code part of
> PG_CATCH() doses not reset NInitialRunningXacts and InitialRunningXacts.
> Then, calling pg_logical_slot_get_changes_guts again, the core may occur.
> Unfortunately, I couldn't find a minimal reproduction case. However, I
> observed an *ERROR: canceling statement due to statement timeout* logged
> before each core occurred. (For some reason, I can't provide the information
> of log)
>
Thanks for the report. I think your analysis is correct and I see that
you have proposed a patch in the next email. I'll look into it and
share my feedback.
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Zhijie Hou (Fujitsu) | 2023-08-17 06:51:02 | RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder() |
Previous Message | PG Bug reporting form | 2023-08-16 06:32:40 | BUG #18058: Http Extension Postgres |