public inbox for [email protected]
help / color / mirror / Atom feedFrom: Euler Taveira <[email protected]>
To: Pradeep Kumar <[email protected]>
To: pgsql-hackers <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Erik Rijkers <[email protected]>
Subject: Re: rare crash - FailedAssertion snapbuild.c Line: 580
Date: Thu, 01 Aug 2024 15:09:15 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJ4xhP=3a4w_-zaU8p0YNZHOZC3nF=L0ERHrXiaM_G0QQA-3ZA@mail.gmail.com>
References: <CAJ4xhPnNB6C=XcrLp_q-=MWzwTcKC9OyhXtpswxrm_UMvCj_PA@mail.gmail.com>
<CAJ4xhP=3a4w_-zaU8p0YNZHOZC3nF=L0ERHrXiaM_G0QQA-3ZA@mail.gmail.com>
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 <[email protected]>
date: Mon, 21 Nov 2022 08:54:43 +0530
committer: Amit Kapila <[email protected]>
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
Discussion: https://postgr.es/m/CAA4eK1L8wYcyTPxNzPGkhuO52WBGoOZbT0A73Le=ZUWYAYmdfw@mail.gmail.com
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).
[1] https://www.postgresql.org/support/versioning/
--
Euler Taveira
EDB https://www.enterprisedb.com/
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: rare crash - FailedAssertion snapbuild.c Line: 580
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox