| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | adam(dot)tomjack(at)zuerchertech(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7906: pg_dump exits successfully after an error |
| Date: | 2013-02-27 18:29:48 |
| Message-ID: | 512E509C.8030300@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2/25/13 7:59 PM, adam(dot)tomjack(at)zuerchertech(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | fburgess | 2013-02-27 21:21:44 | Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space. |
| Previous Message | Michael Enke | 2013-02-27 16:03:07 | Re: BUG #7908: documentation mismatch |