| From: | ow <oneway_111(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, ow <oneway_111(at)yahoo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_restore and create FK without verification check |
| Date: | 2003-11-26 15:37:23 |
| Message-ID: | 20031126153723.7012.qmail@web21402.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > This doesn't really replace pg_dump/pg_restore, because it probably
> > wouldn't be able to upgrade a cluster.
>
> Right, any such physical dump would be limited to restoring a whole
> cluster as-is: no imports into other clusters, no selectivity, no fancy
> games. The main reason is you'd have to dump and restore pg_clog along
> with the data files.
>
But that would not help people who would HAVE to use pg_dump/pg_restore (e.g.
to backup/restore a single schema), would it? Depending on the db size, etc.,
creation of FK constraint(s) may take many hours. How should this be handled
then?
Thanks
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-11-26 15:58:56 | NetBSD Sparc OK |
| Previous Message | Tom Lane | 2003-11-26 15:25:39 | Re: statistics about tamp tables ... |