From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: What happens when wal fails? |
Date: | 2005-08-04 11:15:48 |
Message-ID: | 42F1F8E4.4010805@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Joseph Shraibman wrote:
> If I put the pg_xlog directory on its own disk, then that disk fails,
> does that mean the postgres is hosed or does it just mean that postgres
> no longer safe from a power outage? Does pg detect a problem with the
> wal and then call fsync() on the database files if wal isn't working?
I'm guessing hosed, or at least potentially so. You'd fit a new disk,
restart PG and it would complain that it couldn't re-run the WAL files.
That implies that at least some of your transactions might be lost.
Of course PITR would reduce the danger of this, even if you just copied
the WAL to another disk on the same machine.
I don't know about fsync-ing database files in their absence I'm afraid.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2005-08-04 11:34:56 | Re: Trigger Variables |
Previous Message | Richard Huxton | 2005-08-04 11:12:22 | Re: pgsql-odbc list problem |