Re: Backup and Recovery - Mailing list pgsql-hackers

From Matthew Kirkwood
Subject Re: Backup and Recovery
Date
Msg-id Pine.LNX.4.33.0106211050590.11353-100000@sphinx.mythic-beasts.com
Whole thread Raw
In response to Re: Backup and Recovery  (Naomi Walker <nwalker@eldocomp.com>)
Responses Re: Backup and Recovery  (ncm@zembu.com (Nathan Myers))
List pgsql-hackers
On Wed, 20 Jun 2001, Naomi Walker wrote:

> >You are aware that you can still lose up to (by default) 16Mb
> >worth of transactions in this scheme, I presume?
>
> I'm just starting with Postgresql, but, I thought with fsync on this
> was not the case.  Is that not true or what else did I miss?

I suppose that it rather depends on how you expected to
move the logs over.  My approach was to archive the redo
when PG is done with them and only then to roll them
forward.

If a catastrophe occurs, then I wouldn't be able to do
anything with a half-full log.

Our Oracle setups use redo logs of only 1Mb for this
reason, and it doesn't seem to hurt too much (though
Oracle's datafile formats seem a fair bit denser than
Postgres's).

Matthew.



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: stuck spin lock with many concurrent users
Next
From: Karel Zak
Date:
Subject: Re: nocreatetable for 7.1.2