From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_xlog safety |
Date: | 2003-01-21 21:14:56 |
Message-ID: | 20030121161456.Y18114@mail.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jan 21, 2003 at 03:43:40PM -0500, Vivek Khera wrote:
> So this leads me to my question: one of the tips for performance is to
> move the pg_xlog to its own disk. Now that I have a spare disk I was
> considering moving pg_xlog there. However, that's the only disk that
Test this first. On our Sun A5200 arrays, configured using Veritas
and RAID 1+0, I have tried several times and failed to discover a
performance andvantage by putting the WAL on another disk or pair of
disks. (In other configurations, the same is not the case.)
> wouldn't be RAID protected. What would happen to the db if that disk
> failed? If I were able to perform a clean shutdown, replace that
> disk, and start up postgres again, would it be ok with the pg_xlog
> directory empty? Is it only used for startup after an unclean
> shutdown or for every startup?
I believe you'd need to run pg_resetxlog in this case.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
From | Date | Subject | |
---|---|---|---|
Next Message | Hadley Willan | 2003-01-21 21:53:08 | To Natural Key or Not |
Previous Message | codeWarrior | 2003-01-21 21:08:22 | Re: grant to all tables |