pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux
2+ messages / 2 participants
[nested] [flat]
* BUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux
@ 2025-11-18 22:01 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2025-11-18 22:01 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: jrizelo@gmail.com
The following bug has been logged on the website:
Bug reference: 19119
Logged by: Joelcio Rizelo
Email address: jrizelo@gmail.com
PostgreSQL version: 17.6
Operating system: Ubuntu 24.04.3 LTS (Noble Numbat)
Description:
When executing the materialized view refresh, the error occasionally occurs.
It’s not consistent, but it has been happening frequently after upgrading
from PG13 to PG17.
See logs below:
2025-11-07 00:21:01 -03 [216928]: [124-1] db=, user=, app=, client=LOG:
background worker "parallel worker" (PID 3627154) was terminated by signal
11: Segmentation fault
2025-11-07 00:21:01 -03 [216928]: [125-1] db=, user=, app=, client=DETAIL:
Failed process was running: REFRESH MATERIALIZED VIEW v_remessas_mat WITH
DATA;
2025-11-07 00:21:01 -03 [216928]: [126-1] db=, user=, app=, client=LOG:
terminating any other active server processes
gdb /usr/lib/postgresql/17/bin/postgres
_usr_lib_postgresql_17_bin_postgres.110.crash.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
Core was generated by `postgres: 17/pgdata: parallel worker for PID 3627152
'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 dsa_free (area=0xb600ef7ad850, dp=<optimized out>) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/utils/mmgr/dsa.c:845
warning: 845
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/utils/mmgr/dsa.c:
No such file or directory
(gdb) bt
#0 dsa_free (area=0xb600ef7ad850, dp=<optimized out>) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/utils/mmgr/dsa.c:845
#1 0x0000b600d20c7a3c in ExecHashTableDetachBatch
(hashtable=hashtable@entry=0xb600ef8a5e58) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHash.c:3353
#2 0x0000b600d20c87c8 in ExecParallelHashJoinNewBatch
(hjstate=0xb600ef7dd710) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:1186
#3 ExecHashJoinImpl (parallel=true, pstate=0xb600ef7dd710) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:653
#4 ExecParallelHashJoin (pstate=0xb600ef7dd710) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:700
#5 0x0000b600d20c8340 in ExecProcNode (node=0xb600ef7dd710) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/include/executor/executor.h:275
#6 ExecHashJoinOuterGetTuple (hashvalue=0xffffd91a2610,
hjstate=0xb600ef7dc4a0, outerNode=0xb600ef7dd710) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:908
#7 ExecHashJoinImpl (parallel=false, pstate=0xb600ef7dc4a0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:434
#8 ExecHashJoin (pstate=0xb600ef7dc4a0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:684
#9 0x0000b600d20c6d10 in ExecProcNode (node=0xb600ef7dc4a0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/include/executor/executor.h:275
#10 MultiExecParallelHash (node=0xb600ef7cc740) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHash.c:282
#11 MultiExecHash (node=0xb600ef7cc740) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHash.c:112
#12 0x0000b600d20c8684 in ExecHashJoinImpl (parallel=true,
pstate=0xb600ef7cdda0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:346
#13 ExecParallelHashJoin (pstate=0xb600ef7cdda0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:700
#14 0x0000b600d20c8340 in ExecProcNode (node=0xb600ef7cdda0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/include/executor/executor.h:275
#15 ExecHashJoinOuterGetTuple (hashvalue=0xffffd91a28b0,
hjstate=0xb600ef7cdb10, outerNode=0xb600ef7cdda0) at
/usr/src/postgresql-17-17.6-2.pgdg24.04+1/build/../src/backend/executor/nodeHashjoin.c:908
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux
@ 2025-11-19 06:00 Tom Lane <tgl@sss.pgh.pa.us>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2025-11-19 06:00 UTC (permalink / raw)
To: jrizelo@gmail.com; +Cc: pgsql-bugs@lists.postgresql.org
PG Bug reporting form <noreply@postgresql.org> writes:
> When executing the materialized view refresh, the error occasionally occurs.
> It’s not consistent, but it has been happening frequently after upgrading
> from PG13 to PG17.
There's pretty much zero chance that we can identify this problem
from the given information. Can you create a self-contained
reproducer script? It's okay if it doesn't fail every time,
so long as it fails some of the time.
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-11-19 06:00 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-11-18 22:01 BUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux PG Bug reporting form <noreply@postgresql.org>
2025-11-19 06:00 ` Re: BUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux Tom Lane <tgl@sss.pgh.pa.us>
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