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

Re: [BUGS] 8.0: Absolute path required for INITDB?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] 8.0: Absolute path required for INITDB?
Date: 2004-08-16 16:09:12
Message-ID: 4120DC28.4070705@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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




In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-08-16 16:13:05
Subject: Re: BUG #1208: Invalid page header
Previous:From: Bruce MomjianDate: 2004-08-16 16:00:01
Subject: Re: [PATCHES] Bug: century/millenium still broken

pgsql-patches by date

Next:From: Tom LaneDate: 2004-08-16 16:21:32
Subject: Re: [BUGS] 8.0: Absolute path required for INITDB?
Previous:From: Bruce MomjianDate: 2004-08-16 16:00:01
Subject: Re: [PATCHES] Bug: century/millenium still broken

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