From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | johnsw(at)wardbrook(dot)com |
Cc: | "Cott Lang" <cott(at)internetstaff(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: tablespaces a priority for 7.5? |
Date: | 2004-01-22 17:24:30 |
Message-ID: | 12954.1074792270@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"John Sidney-Woollett" <johnsw(at)wardbrook(dot)com> writes:
> With Oracle you have the option of EITHER exporting the database
> (equivalent to doing pg_dump) OR taking the database offline and carrying
> out a file system level copy of the database files.
The planned PITR feature would not require you to take anything offline.
The whole concept of an "offline" database is an Oracle-ism that I see
no value in emulating.
> One caveat for Oracle (at least in 8.1.x) is that DDL statements are not
> recorded in the archive logs, and can screw things up. Best to take a new
> export/dump after making DDL changes!
Well, we're ahead of them on that...
> The difference between Oracle and Postgres appears to be that posgres
> requires a file system level copy of the database instead of being able to
> make use of a dump file for this type of recovery. Is that correct?
I dunno what a "dump file" would equate to in Postgres terms, but yeah,
we're envisioning using ordinary filesystem tools (tar, say) as the
mechanism for handling a baseline backup.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-01-22 17:26:47 | Re: Lost plpgsql function |
Previous Message | Steve Atkins | 2004-01-22 17:21:27 | Re: embedded/"serverless" (Re: serverless postgresql) |