Re: BUG #4344: initdb -L timezone directory - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4344: initdb -L timezone directory
Date
Msg-id 13406.1218125046@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4344: initdb -L timezone directory  ("Domingo Alvarez Duarte" <mingodad@gmail.com>)
Responses Re: BUG #4344: initdb -L timezone directory
List pgsql-bugs
"Domingo Alvarez Duarte" <mingodad@gmail.com> writes:
> I expected initdb to use "-L" value to timezone too and for all other files
> that is expected to be on share directory.

-L only affects where initdb looks for its own input files; it has
nothing to do with where the backend looks for the PGSHAREDIR files.

I rather wonder whether -L has any reason to live at all.  initdb's
default is to locate PGSHAREDIR relative to where it finds the backend
executable, which is consistent with what the backend itself is going
to do.  Is there any scenario where specifying a different location
wouldn't be broken?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4345: ERROR: OUT OF MEMORY
Next
From: Chris Schroter
Date:
Subject: Postgres Vacuum Password