BUG #7906: pg_dump exits successfully after an error
The following bug has been logged on the website:
Bug reference: 7906
Logged by: Adam Tomjack
Email address: adam.tomjack@zuerchertech.com
PostgreSQL version: 9.2.1
Operating system: Linux 2.6.32-39-server #86-Ubuntu SMP x86_64
Description:
I have a database that uses a user-defined datatype. If the .so file
implementing that type is missing, pg_dump will fail when dumping a table
which uses that type, but it will still exit with status 0. The dump file
will be truncated and invalid.
Output:
pg_dump: Dumping the contents of table "foo" failed: PQgetResult() failed.
pg_dump: Error message from server: ERROR: could not access file
"bar-type": No such file or directory
pg_dump: The command was: COPY public.foo (baz) TO stdout;
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 2/25/13 7:59 PM, adam.tomjack@zuerchertech.com wrote:
I have a database that uses a user-defined datatype. If the .so file
implementing that type is missing, pg_dump will fail when dumping a table
which uses that type, but it will still exit with status 0. The dump file
will be truncated and invalid.Output:
pg_dump: Dumping the contents of table "foo" failed: PQgetResult() failed.
pg_dump: Error message from server: ERROR: could not access file
"bar-type": No such file or directory
pg_dump: The command was: COPY public.foo (baz) TO stdout;
I can reproduce exactly this output, but the exit status is 1.
Can we see the exact pg_dump command that you are executing?
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs