| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Amiel <becauseimjeff(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump/restore and functions/triggers/trigger functions |
| Date: | 2007-02-07 03:16:36 |
| Message-ID: | 29516.1170818196@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeff Amiel <becauseimjeff(at)yahoo(dot)com> writes:
> I guess the real question is (other than related to this issue), it there any need to dump the catalog/informational schemas?
There isn't, but pg_dump won't dump them anyway; you have no need to
specify switches for that.
The whole business of partial dumps and selective restores is still
pretty messy :-(. IIRC pg_dump doesn't have any concept of dumping
or restoring all the objects that a desired object depends on; but
without that, any kind of selectivity is hard to use. My recommendation
at the moment is to always do complete dumps --- you can filter during
pg_restore if you have to, but if your back is against the wall and your
only up-to-date dump is critically incomplete, you're screwed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2007-02-07 04:13:46 | Re: Locking question? |
| Previous Message | Kevin Field | 2007-02-07 02:25:35 | Re: getting status transaction error |