| From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | pg_dump superflous warning message |
| Date: | 2010-02-11 17:08:54 |
| Message-ID: | 20100211120854.2f4c0c20.wmoran@potentialtech.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
If I do:
pg_dump -a --disable-triggers
I get a warning message:
pg_dump: NOTICE: there are circular foreign-key constraints among these table(s):
pg_dump: directory
pg_dump: You may not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
Of course, this was confusing as hell -- we spent a good bit of time
trying to figure out why pg_dump wasn't honoring --disable-triggers.
It turns out that it is, it's just that it prints the warning even
when it's not applicable.
At least from my perspective, I don't think this warning should be
printed if the proper command line switches have been given. Is there
a good reason to print it anyway?
This is with pg 8.4.2 (both client and server).
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moe | 2010-02-11 17:11:45 | Re: Searching a DB index.. possible? |
| Previous Message | Richard Huxton | 2010-02-11 16:56:51 | Re: Searching a DB index.. possible? |