Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
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?
That wa
Andrew Dunstan wrote:
>
>
> 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
> descripti
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> 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?
That was to avoid a Win
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 c
Patch to throw an error if -L is not an abolute path attached and
applied.
---
Josh Berkus wrote:
> 8.0 beta CVS of 8/8/2004:
>
> If a relative path is used for the -L option in initdb, the following fatal
> error happens:
