pg_dump doesn't report failure

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_dump doesn't report failure
Date: 2002-03-08 01:22:35
Message-ID: GNELIHDDFBOCMGBFGEFOKEKMCBAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I was just bitten by an issue in pg_dump where if the table it is to dump
doesn't exist, it doesn't return an error or anything! We only just
realised that a dump script we wrote had a typo in it, and all our 'backups'
are invalid...

This is the current CVS behaviour:

bash-2.05$ pg_dump -a -t badtable mydb
--
-- Selected TOC Entries:
--

Where 'badtable' is the name of a table that doesn't exist.

Should this beheaviour be at least modified to write something to stderr?

Chris

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Brent Verner 2002-03-08 01:25:36 Re: [PATCHES] system catalog relation of a table and a serial sequence
Previous Message Bruce Momjian 2002-03-08 01:16:26 Re: new module contrib/tree for 7.2 ?