Re: [BUGS] 8.0: Absolute path required for INITDB? - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: [BUGS] 8.0: Absolute path required for INITDB?
Date
Msg-id 4120DC28.4070705@dunslane.net
Whole thread Raw
In response to Re: [BUGS] 8.0: Absolute path required for INITDB?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [BUGS] 8.0: Absolute path required for INITDB?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [BUGS] 8.0: Absolute path required for INITDB?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches

Bruce Momjian wrote:

>Patch to throw an error if -L is not an abolute path attached and
>applied.
>
>


Why are we placing this restriction? What Josh tried to do seems
perfectly reasonable to me. Rather I would ask why we changed the
description-loading routine in version 1.7 of initdb.c to use a copy
from file instead of what happens everywhere else where initdb loads the
file and feeds it to the postgres stdin? And if we want to keep doing
that rather than being consistent with the rest of initdb, can't we just
make sure we make the path absolute?

cheers

andrew




pgsql-patches by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Postgresql.conf Documentation change
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] 8.0: Absolute path required for INITDB?