pg_dump segfaults with publication
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t36183psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 07:58 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t36183_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t36183_1 && git checkout t36183_1Patchset v1 (message #1) is on t36183_1
Hi,
pg_dump segfaults if there are more than one DO_PUBLICATION_REL objects to
dump.
create table foo (a int);
create publication foo_pub;
alter publication foo_pub add table foo;
$ pg_dump
<OK>
create table bar (a int);
alter publication foo_pub add table bar;
$ pg_dump -s
Segmentation fault (core dumped)
The reason is DumpableObject.name is not set being set in
getPublicationTables(). Attached patch fixes that.
Thanks,
Amit
On 3/6/17 03:06, Amit Langote wrote:
pg_dump segfaults if there are more than one DO_PUBLICATION_REL objects to
dump.
Fix committed with a test case. Thanks.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers