Make pg_dump behave more sanely when built without HAVE_LIBZ. For some reason the code to emit a warning and switch to uncompressed output was placed down in the guts of pg_backup_archiver.c. This is definitely too late in the case of parallel operation (and I rather wonder if it wasn't too late for other purposes as well). Put it in pg_dump.c's option-processing logic, which seems a much saner place.
Also, the default behavior with custom or directory output format was to emit the warning telling you the output would be uncompressed. This seems unhelpful, so silence that case. Back-patch to 9.3 where parallel dump was introduced. Kyotaro Horiguchi, adjusted a bit by me Report: <[email protected]> Branch ------ REL9_4_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/f2f18a37c335384240c4f6b5ebbed4678ae8949c Modified Files -------------- src/bin/pg_dump/pg_backup_archiver.c | 10 ---------- src/bin/pg_dump/pg_dump.c | 9 +++++++++ 2 files changed, 9 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
