Don Baccus Wrote...
> 
> At 09:09 PM 6/29/99 -0400, Bruce Momjian wrote:
>   
> >> Just out of curiosity, I did a DUMP on the database while running a script
> >> that ran a pile of updates. When I restored the database files, it was so
> >> corrupted that I couldn't even run a select. vacuum just core dumped...
> 
> >When you say DUMP, you mean pg_dump, right?  Are you using 6.5?
> 
> In his first note, he was proposing a scheme that would allow either
> filesystem dumps or pg_dumps, which I think a couple of respondents
> missed.
> 
> So I suspect he means a filesystem dump in this case.  Which of course
> won't work in postgres, or in Oracle.

ISTR...

Oracle has a way to mark tablespaces for backup.  Once you do this you can
then copy the data files, and then release the tablespace.  I guess while
the backup is happening all the transactions go to the redo log (or is
it the other log).  I'm a bit fuzzy about the details but it is a nice
feature.  You don't have to dump the database, just copy off the data
files to tape or whatever.

When you restore from backups there are some incantations required
to bring things back into sync.

Someone else can undoubtedly explain this much more clearly.

-- cary
Cary O'Brien
cobrien@radix.net




Wed, 30 Jun 1999 15:48:01 -0400 (EDT)
"Cary O'Brien" <cobrien@Radix.Net>
Oracle and hot backups