From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Crash Recovery, pt 2
Date: 24 Jan 2003 08:12:19 -0600
Message-ID: <1043417539.29437.82.camel@haggis> (raw)
In-Reply-To: <20030124082219.B26558@mail.libertyrms.com>
References: <2147483647.1043361178@[10.0.1.133]>
<20030124082219.B26558@mail.libertyrms.com>
On Fri, 2003-01-24 at 07:22, Andrew Sullivan wrote:
> On Thu, Jan 23, 2003 at 10:32:58PM -0500, Noah Silverman wrote:
> > To preface my question, we are still in the process of evaluating postgres
> > to determine if we want to switch our production environment over.
> >
> > I'm curious about where I can find documentation about crash recovery in
> > postgres. In mysql, there is a nice table recovery utility (myisamchk).
>
> It recovers automatically. Make sure you run with fsync turned on.
> That calls fsync on the WAL at the point of every COMMIT, and COMMIT
> isn't finished before the fsync returns. Then, in case of a crash,
> the WAL just plays back and fixes up the data area.
On commercial databases, there's a command to flush the roll-forward
logs to tape at intervals during the day.
Thus, if the disk(s) get corrupted, one can restore the database to
new disks, then apply the on-tape roll-forward logs to the database,
and you'd have only lost a few hours of data, instead of however
many hours (or days) it's been since the last database backup.
Also, flushing them to tape (or a different partition) ensures that
they don't fill up the partition during a particularly intensive
batch job.
Are there any FM's that explain how this works in Postgres?
Thanks,
Ron
--
+---------------------------------------------------------------+
| Ron Johnson, Jr. mailto:ron.l.johnson@cox.net |
| Jefferson, LA USA http://members.cox.net/ron.l.johnson |
| |
| "Fear the Penguin!!" |
+---------------------------------------------------------------+
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: ron.l.johnson@cox.net
Subject: Re: Crash Recovery, pt 2
In-Reply-To: <1043417539.29437.82.camel@haggis>
References: <2147483647.1043361178@[10.0.1.133]> <20030124082219.B26558@mail.libertyrms.com> <1043417539.29437.82.camel@haggis>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox