On Nov 9, 2008, at 11:44 AM, Tom Lane wrote:
> Decibel! <decibel@decibel.org> writes:
>> On Nov 8, 2008, at 3:08 PM, Tom Lane wrote:
>>> ... It's reasonably common for pg_xlog to be a symlink.
>
>> ISTM it'd be better still to have an official knob that allows you to
>> determine where pg_xlog lives. ISTR discussion about that, but I
>> don't see anything obvious in postgresql.conf or configure.
>
> My recollection of the discussion is that we decided it was too
> dangerous to make it "configurable" --- if you crash and restart
> and the
> restart seizes on some other WAL directory to recover from, you're up
> the proverbial creek.
>
> (Come to think of it, this is also a reasonable argument for not
> letting
> postmaster startup auto-create pg_xlog ...)
What if the the location was recorded in something that's not meant
to be touched by users, such as pg_control? At that point we'd have a
command for actually moving it.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828