From: Álvaro Herrera <alvherre@kurilemu.de>
To: postgresql@zr40.nl
To: pgsql-bugs@lists.postgresql.org
Cc: Peter Geoghegan <pg@bowt.ie>
Subject: Re: BUG #19082: Failing assert in index scan
Date: Fri, 10 Oct 2025 13:14:19 +0200
Message-ID: <202510101109.xc4mj5lzidv7@alvherre.pgsql> (raw)
In-Reply-To: <19082-628e62160dbbc1c1@postgresql.org>
On 2025-Oct-10, PG Bug reporting form wrote:
> Last week, I've noticed a crash due to a failed assertion that was
> consistently being triggered by an application every 10 seconds. Here's the
> log:
>
> ---
> TRAP: failed Assert("!XLogRecPtrIsInvalid(so->currPos.lsn)"), File:
> "./build/../src/backend/access/nbtree/nbtutils.c", Line: 1782, PID: 394782
> postgres: mastodon mastodon_production [local]
> SELECT(ExceptionalCondition+0x75) [0x55f9c3027ea5]
AFAICS this assertion is new as of commit c7f25feb3862. Peter?
I find it rather odd that you're running a production instance compiled
with assertions enabled, though. They have a considerable impact on
performance, and should be used for development or testing only, not
production. I would recommend to recompile with assertions disabled.
Also, it might well be that the assertion is buggy, and that nothing
would go wrong if that assertion is removed and just let the `if` test
below handle the case.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
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: pgsql-bugs@postgresql.org
Cc: alvherre@kurilemu.de, postgresql@zr40.nl, pgsql-bugs@lists.postgresql.org, pg@bowt.ie
Subject: Re: BUG #19082: Failing assert in index scan
In-Reply-To: <202510101109.xc4mj5lzidv7@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox