BUG #7906: pg_dump exits successfully after an error - Mailing list pgsql-bugs

From adam.tomjack@zuerchertech.com
Subject BUG #7906: pg_dump exits successfully after an error
Date
Msg-id E1UA8tE-0004a6-9K@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #7906: pg_dump exits successfully after an error  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-bugs
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;

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #7902: lazy cleanup of extraneous WAL files can cause out of disk issues
Next
From: jimbob
Date:
Subject: Re: BUG #7853: Incorrect statistics in table with many dead rows.