Re: rare crash - FailedAssertion snapbuild.c Line: 580 - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: rare crash - FailedAssertion snapbuild.c Line: 580
Date
Msg-id e0209c4e-dc9d-484c-a869-4168a6cae4b5@app.fastmail.com
Whole thread Raw
In response to Re: rare crash - FailedAssertion snapbuild.c Line: 580  (Pradeep Kumar <spradeepkumar29@gmail.com>)
Responses Re: rare crash - FailedAssertion snapbuild.c Line: 580
List pgsql-hackers
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).




--
Euler Taveira

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: On disable_cost
Next
From: Jeff Davis
Date:
Subject: Inconsistency with EXPLAIN ANALYZE CREATE MATERIALIZED VIEW