[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: [BUGS] BUG #7906: pg_dump exits successfully after an error
From:       Peter Eisentraut <peter_e () gmx ! net>
Date:       2013-02-27 18:29:48
Message-ID: 512E509C.8030300 () gmx ! net
[Download RAW message or body]

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
[prev in list] [next in list] [prev in thread] [next in thread]