From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 8.1beta2 pg_dumpall inconsistencies |
Date: | 2005-10-02 14:59:18 |
Message-ID: | 3249.1128265158@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> [jd(at)jd pgsqldev]$ bin/pg_dumpall -U jd -D -o -p 5500
> ...
> pg_dump: INSERT (-d, -D) and OID (-o) options cannot be used together
> pg_dump: (The INSERT command cannot set OIDs.)
> pg_dumpall: pg_dump failed on database "postgres", exiting
> Why am I getting a partial dump when the options are not compatible?
Because -D and -o are pg_dump options, which pg_dumpall just passes down
without inspection. I'm not sure that it makes sense to try to
replicate pg_dump's validity checking logic in pg_dumpall; I fear we'd
be more likely to cause problems by letting them get out of sync than
to solve problems by complaining a little sooner.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2005-10-02 15:12:23 | Re: Socket problem using beta2 on Windows-XP |
Previous Message | Martijn van Oosterhout | 2005-10-02 13:30:51 | Re: effective SELECT from child tables |