From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: edwin.polkerman@splendiddata.com
Subject: BUG #16981: pg_dump errors out with incompatible option set but empty tar dump file is created as result
Date: Fri, 23 Apr 2021 10:54:43 +0000
Message-ID: <16981-df7cf847e31caada@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16981
Logged by: Edwin Polkerman
Email address: edwin.polkerman@splendiddata.com
PostgreSQL version: 13.2
Operating system: Centos7/8, RHEL7/8, SUSE12/15
Description:
Basically it is more an improvement than a real bug
Run the following pg_dump command:
> pg_dump -h 10.17.0.12 -p 5432 -d postgres -U splendid -f
/home/splendid/pg_dump_file.tar -F t -v --compress=4
As expected pg_dump returns an error:
pg_dump: error: compression is not supported by tar archive format
What was not expected is that the file pg_dump_file.tar is created (with 0
size)
> ls -l /home/splendid
-rw-rw-r-- 1 splendid splendid 0 Apr 23 12:50 pg_dump_file.tar
To my opinion the dump file should not be created because the check on
options provided can be done before creating the result file
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, edwin.polkerman@splendiddata.com
Subject: Re: BUG #16981: pg_dump errors out with incompatible option set but empty tar dump file is created as result
In-Reply-To: <16981-df7cf847e31caada@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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