pg_dump:qemu: uncaught target signal 7 (Bus error) - core dumped

From: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: pg_dump:qemu: uncaught target signal 7 (Bus error) - core dumped
Date: 2025-12-08 17:53:53
Message-ID: CAC6VRobi3BEuFM-Yjr=VteyWh4tvs_tnL10KGsCzthZsfw7TSQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
I found a scenario where, after firing the wrong way of using the pg_dump
command, not only server fail to start,
But later, I am not able to perform initdb/pg_ctl as well

Please refer to this testcase:
"
PG v19 devel, Cluster running on default port=5432
Run pg_dump (./pg_dump -Ft -s -c -v -f postgres schema_clean.tar1)
"

The result is :
edb(at)1a1c15437e7c bin]$ ./pg_dump -Ft -s -c -v -f postgres
schema_clean.tar1
qemu: uncaught target signal 7 (Bus error) - core dumped
qemu-x86_64:qemu-x86_64:qemu-x86_64: QEMU internal SIGBUS {code=ADRERR,
addr=0x8c6b70}QEMU internal SIGBUS {code=ADRERR, addr=0x8c6b70}
QEMU internal SIGBUS {code=ADRERR, addr=0x8c6b70}
qemu-x86_64:qemu-x86_64: QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
qemu-x86_64: QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
qemu-x86_64:qemu-x86_64: QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
QEMU internal SIGBUS {code=ADRERR, addr=0xa7cee0}
pg_dump: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed:
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

The correct way is to use
./pg_dump -Ft -s -c -v -f schema_clean.tar1 postgres

Is there any way we can generate some error messages?

regards,

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-12-08 18:03:18 Re: Moving _bt_readpage and _bt_checkkeys into a new .c file
Previous Message tushar 2025-12-08 17:09:00 Re: Non-text mode for pg_dumpall