From: | adam(dot)tomjack(at)zuerchertech(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #7906: pg_dump exits successfully after an error |
Date: | 2013-02-26 00:59:28 |
Message-ID: | E1UA8tE-0004a6-9K@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 7906
Logged by: Adam Tomjack
Email address: adam(dot)tomjack(at)zuerchertech(dot)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;
From | Date | Subject | |
---|---|---|---|
Next Message | ibrahimkocaoglutr | 2013-02-26 08:30:05 | BUG #7907: BEFORE DELETE TRIGGER (not instead of, my trigger BEFORE)not row delete... |
Previous Message | jimbob | 2013-02-25 19:00:10 | Re: BUG #7853: Incorrect statistics in table with many dead rows. |