Re: [PATCHES] xlog directory at initdb time - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] xlog directory at initdb time
Date
Msg-id 3560.1167751110@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] xlog directory at initdb time  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCHES] xlog directory at initdb time  (Bruce Momjian <bruce@momjian.us>)
Re: [PATCHES] xlog directory at initdb time  (Casey Duncan <casey@pandora.com>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Am Mittwoch, 27. Dezember 2006 02:56 schrieb Euler Taveira de Oliveira:
>> This simple patch lets someone specifies the xlog directory at initdb
>> time. It uses symlinks to do it, and create and/or set permissions at
>> the directory as appropriate.

> We already had this functionality in initdb a few versions ago.  Did you 
> review why it was removed?

The discussion thread seems to start here:

http://archives.postgresql.org/pgsql-hackers/2002-08/msg00306.php

As best I can tell the objections came from the fact that Thomas had
implemented it as a postmaster-start-time switch, which made it a
foot-gun because you could mistakenly start the postmaster with a
different XLOG than you were using before.  That would not apply to a
symlink-made-by-initdb approach.  All this is doing is formalizing
something we already suggest people do by hand...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Reverse-sort indexes and NULLS FIRST/LAST sorting
Next
From: Tom Lane
Date:
Subject: Re: effective_cache_size vs units