Thread: rare crash - FailedAssertion snapbuild.c Line: 580
Hello all,
Message Id: https://www.postgresql.org/message-id/flat/3808dc548e144c860fc3fe57de013809%40xs4all.nl#72629a188e99e14387230fccc8eef518
Actually I'm also facing this issue. Any solution regarding this? .Kindly give me the explanation of why this error occurs.
Thanks and regards
Pradeep
Message Id: https://www.postgresql.org/message-id/flat/3808dc548e144c860fc3fe57de013809%40xs4all.nl#72629a188e99e14387230fccc8eef518
Actually I'm also facing this issue. Any solution regarding this? .Kindly give me the explanation of why this error occurs.
Thanks and regards
Pradeep
Hello all,
Any update on this?
Thanks and regards
Pradeep
Thanks and regards
Pradeep
On Thu, Jul 25, 2024 at 1:09 PM Pradeep Kumar <spradeepkumar29@gmail.com> wrote:
Hello all,
Message Id: https://www.postgresql.org/message-id/flat/3808dc548e144c860fc3fe57de013809%40xs4all.nl#72629a188e99e14387230fccc8eef518
Actually I'm also facing this issue. Any solution regarding this? .Kindly give me the explanation of why this error occurs.
Thanks and regards
Pradeep
On Thu, Aug 1, 2024, at 6:59 AM, Pradeep Kumar wrote:
Any update on this?
Are you using version 11? This version is obsolete and is not supported
anymore. Consider a supported version [1].
Per the following commit (in version 16), this Assert was replaced by
elog.
commit: 240e0dbacd390a8465552e27c5af11f67d747adb
author: Amit Kapila <akapila@postgresql.org>
date: Mon, 21 Nov 2022 08:54:43 +0530
committer: Amit Kapila <akapila@postgresql.org>
date: Mon, 21 Nov 2022 08:54:43 +0530
Add additional checks while creating the initial decoding snapshot.
As per one of the CI reports, there is an assertion failure which
indicates that we were trying to use an unenforced xmin horizon for
decoding snapshots. Though, we couldn't figure out the reason for
assertion failure these checks would help us in finding the reason if the
problem happens again in the future.
Author: Amit Kapila based on suggestions by Andres Freund
Reviewd by: Andres Freund
According to this discussion, there isn't a clue about the root cause.
If you have a test case, share it (mainly if you are observing it in
version 16+ that exposes some data which may be useful for analysis).
Hello Euler,
01.08.2024 21:09, Euler Taveira wrote:
According to this discussion, there isn't a clue about the root cause.01.08.2024 21:09, Euler Taveira wrote:
If you have a test case, share it (mainly if you are observing it in
version 16+ that exposes some data which may be useful for analysis).
Please take a look at [1], where I presented a reproducer for apparently
the same issue.
[1] https://www.postgresql.org/message-id/b91cf8ef-b5af-5def-ff05-bd67336ef907%40gmail.com
Best regards,
Alexander