The following bug has been logged on the website: Bug reference: 7809 Logged by: Joe Van Dyk Email address: j...@tanga.com PostgreSQL version: 9.2.2 Operating system: Ubuntu Description:
Running pg_dump on a streaming replication slave with a database that has unlogged_tables will fail unless you provide the "--no-unlogged-table-data" option with the following (scary) error: pg_dump: Dumping the contents of table "tracking_import_data" failed: PQgetResult() failed. pg_dump: Error message from server: ERROR: could not open file "base/16388/190326": No such file or directory pg_dump: The command was: COPY public.tracking_import_data (uuid, tracking_number) TO stdout; (this guy encountered the error as well: http://www.postgresql.org/message-id/de2de764-307d-4a23-a9a9-6608ac097...@ticketevolution.com ) Could running pg_dump against a slave always use the "--no-unlogged-table-data" option? In my case, I had automatic scripts that run pg_dump (without the unlogged option) against the slave, and they failed right after I added an unlogged table for the first time. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
