From: | Kevin Brown <kevin(at)sysexperts(dot)com> |
---|---|
To: | "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-27 02:35:32 |
Message-ID: | 20031127023531.GL6073@filer |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> >> In principle you could do this today, but we don't have enough
> >> support code in place to make it work smoothly, eg WAL segment files
> >> aren't labeled with enough identifying information to let you manage
> >> an archive full of 'em. Still it doesn't seem that far away.
>
> > So I issue CHECKPOINT, and tar the cluster or database. Still, I got two
> > questions:
> > - how to restore a single database
>
> You don't. As I said, any physical backup is going to be
> all-or-nothing. These techniques are not a replacement for pg_dump.
But this is just an artifact of the fact that the WAL is a single
instance-wide entity, rather than a per-database entity. But since
databases are completely separate entities that cannot be simultaneously
accessed by any query (corrections welcome), there isn't any reason in
principle that the WAL files cannot also be created on a per-database
basis.
I'm sure, of course, that doing so would bring with it a new set of
problems and tradeoffs, so it might not be worth it...
--
Kevin Brown kevin(at)sysexperts(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-11-27 02:53:52 | Re: detecting poor query plans |
Previous Message | Christopher Kings-Lynne | 2003-11-27 02:27:22 | 7.5 Plans |