Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] xlog directory at initdb time

From: Casey Duncan <casey(at)pandora(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org,Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Subject: Re: [PATCHES] xlog directory at initdb time
Date: 2007-01-02 19:43:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
On Jan 2, 2007, at 7:18 AM, Tom Lane wrote:

> Peter Eisentraut <peter_e(at)gmx(dot)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:
> 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...

I guess the downside there is that it won't work on platforms that  
don't support symlinks, whereas the postmaster switch would. Not that  
I condone using such platforms ;^)


In response to


pgsql-hackers by date

Next:From: Stephen FrostDate: 2007-01-02 19:50:15
Subject: Re: TODO: GNU TLS
Previous:From: David BorehamDate: 2007-01-02 19:25:34
Subject: Re: TODO: GNU TLS

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-01-02 20:01:50
Subject: Re: [HACKERS] [BUGS] BUG #2846: inconsistent and
Previous:From: Bruce MomjianDate: 2007-01-02 19:00:27
Subject: Re: [PATCHES] xlog directory at initdb time

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group