| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump doesn't report failure |
| Date: | 2002-03-08 02:21:53 |
| Message-ID: | 26197.1015554113@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> 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?
I dunno. I think the direction we were planning to go in was that -t's
argument should be treated as a pattern to match against table names
(eg, a regexp). It's not clear that zero matches are an error when
you are thinking in those terms. On the other hand I can see your point
about not realizing your "backup" isn't.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-03-08 02:58:36 | Re: pg_dump doesn't report failure |
| Previous Message | Tom Lane | 2002-03-08 02:13:40 | Re: point in time recovery and moving datafiles online |