Re: Specifying xlog directory during initdb is failing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Devrim GÜNDÜZ <devrim(at)CommandPrompt(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Specifying xlog directory during initdb is failing
Date: 2008-06-02 02:27:25
Message-ID: 811.1212373645@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <devrim(at)CommandPrompt(dot)com> writes:
> I was testing -X option, and I cannot make it work. This is PostgreSQL
> 8.3.1 on Fedora 9:

> -bash-3.2$ initdb -d -X xlog/ -D data/

The root of the problem is that you can't use a relative path for -X:
it's not clear whether the path is relative to $PGDATA or the working
directory when you invoked initdb, and different bits of initdb
effectively make each of those assumptions. I agree that the failure
mode is pretty opaque :-(. I think the simplest solution is to reject
non-absolute path for -X; is there any real use-case for allowing it?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Sullivan 2008-06-02 02:57:08 Re: Specifying xlog directory during initdb is failing
Previous Message Joe Conway 2008-06-01 23:58:05 Re: [BUGS] BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code