Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: n(dot)kalinin(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
Date: 2025-04-25 06:51:13
Message-ID: CAFiTN-tWeuWWih3tca0oP0vKtj_xXEwY-6FcJXTu=FmioD_siw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Apr 25, 2025 at 11:54 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 18903
> Logged by: Nikita Kalinin
> Email address: n(dot)kalinin(at)postgrespro(dot)ru
> PostgreSQL version: 17.4
> Operating system: ubuntu 22.04
> Description:
>
> Hello. I might be doing something strange, but I’d like to understand why
> this all ends with a SIGABRT.
> After building PostgreSQL like this:
> ./configure --enable-tap-tests --enable-debug --with-openssl
> --enable-cassert --prefix=/tmp/pg && make -j8
> And running these two files:

I tried using the steps you provided, but had no luck. While testing,
I noticed that a lot of steps [1] in your test will fail because the
vacuum can not be run within a transaction block. Is that part of
reproducing the issue? I am looking through the call stack.
Meanwhile, if you can recheck the steps you provided, then it would be
helpful for analysis.

[1]
BEGIN;
CLUSTER pg_class USING pg_class_oid_index;
CLUSTER pg_class USING pg_class_oid_index;
VACUUM FULL pg_class;
VACUUM FULL pg_class;
VACUUM FULL pg_class;

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Никита Калинин 2025-04-25 07:00:41 Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
Previous Message PG Bug reporting form 2025-04-25 05:20:33 BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"