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

From Peter Eisentraut
Subject Re: BUG #7906: pg_dump exits successfully after an error
Date
Msg-id 512E509C.8030300@gmx.net
Whole thread Raw
In response to BUG #7906: pg_dump exits successfully after an error  (adam.tomjack@zuerchertech.com)
List 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?

pgsql-bugs by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.
Next
From: Michael Enke
Date:
Subject: Re: BUG #7908: documentation mismatch