Re: BUG #18893: Segfault during analyze pg_database - Mailing list pgsql-bugs

From Robins Tharakan
Subject Re: BUG #18893: Segfault during analyze pg_database
Date
Msg-id CAEP4nAzFvFfj5kfJcBLQ1HVQwuydABCD2=rzPbM7Fn2WiEptGQ@mail.gmail.com
Whole thread Raw
In response to BUG #18893: Segfault during analyze pg_database  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18893: Segfault during analyze pg_database
List pgsql-bugs

On Sat, 12 Apr 2025 at 13:05, PG Bug reporting form <noreply@postgresql.org> wrote:
>
>
> Creating a few Databases followed by CHECKPOINT causes a segfault.
>

Simply running pgbench (or any workload that triggers AV) causes a segfault.

(gdb) bt
#0  PopActiveSnapshot () at snapmgr.c:766
#1  0x000055a93d8bb02c in vacuum (relations=0x55a9715e7530, params=0x55a9715d4b10, bstrategy=0x55a9715cb050, vac_context=0x55a9715e73e0, isTopLevel=true) at vacuum.c:611
#2  0x000055a93dac2463 in autovacuum_do_vac_analyze (tab=0x55a9715d4b08, bstrategy=0x55a9715cb050) at autovacuum.c:3160
#3  0x000055a93dac119b in do_autovacuum () at autovacuum.c:2439
#4  0x000055a93dabfd3c in AutoVacWorkerMain (startup_data=0x0, startup_data_len=0) at autovacuum.c:1594
#5  0x000055a93dac6aee in postmaster_child_launch (child_type=B_AUTOVAC_WORKER, child_slot=2022, startup_data=0x0, startup_data_len=0, client_sock=0x0) at launch_backend.c:290
#6  0x000055a93dacdab5 in StartChildProcess (type=B_AUTOVAC_WORKER) at postmaster.c:3973
#7  0x000055a93dacdc44 in StartAutovacuumWorker () at postmaster.c:4037
#8  0x000055a93dacd705 in process_pm_pmsignal () at postmaster.c:3794
#9  0x000055a93daca83a in ServerLoop () at postmaster.c:1695
#10 0x000055a93daca209 in PostmasterMain (argc=3, argv=0x55a9714acf90) at postmaster.c:1400
#11 0x000055a93d97222a in main (argc=3, argv=0x55a9714acf90) at main.c:227



(gdb) bt
#0  PopActiveSnapshot () at snapmgr.c:766
#1  0x000055a93d8bb02c in vacuum (relations=0x55a9715dd790, params=0x55a9715cb608, bstrategy=0x55a9715cabe0, vac_context=0x55a9715dd640, isTopLevel=true) at vacuum.c:611
#2  0x000055a93dac2463 in autovacuum_do_vac_analyze (tab=0x55a9715cb600, bstrategy=0x55a9715cabe0) at autovacuum.c:3160
#3  0x000055a93dac119b in do_autovacuum () at autovacuum.c:2439
#4  0x000055a93dabfd3c in AutoVacWorkerMain (startup_data=0x0, startup_data_len=0) at autovacuum.c:1594
#5  0x000055a93dac6aee in postmaster_child_launch (child_type=B_AUTOVAC_WORKER, child_slot=2022, startup_data=0x0, startup_data_len=0, client_sock=0x0) at launch_backend.c:290
#6  0x000055a93dacdab5 in StartChildProcess (type=B_AUTOVAC_WORKER) at postmaster.c:3973
#7  0x000055a93dacdc44 in StartAutovacuumWorker () at postmaster.c:4037
#8  0x000055a93dacd705 in process_pm_pmsignal () at postmaster.c:3794
#9  0x000055a93daca83a in ServerLoop () at postmaster.c:1695
#10 0x000055a93daca209 in PostmasterMain (argc=3, argv=0x55a9714acf90) at postmaster.c:1400
#11 0x000055a93d97222a in main (argc=3, argv=0x55a9714acf90) at main.c:227


-
robins
https://robins.in

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
Next
From: Kirill Reshke
Date:
Subject: Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.