Re: Strange issue with initdb on 8.0 and Solaris automounts - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Strange issue with initdb on 8.0 and Solaris automounts
Date
Msg-id 22095.1106869848@sss.pgh.pa.us
Whole thread Raw
In response to Re: Strange issue with initdb on 8.0 and Solaris automounts  (Kenneth Lareau <elessar@numenor.org>)
Responses Re: Strange issue with initdb on 8.0 and Solaris automounts  (Kenneth Lareau <elessar@numenor.org>)
Re: Strange issue with initdb on 8.0 and Solaris automounts  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Kenneth Lareau <elessar@numenor.org> writes:
> In message <21723.1106868138@sss.pgh.pa.us>, Tom Lane writes:
>> I suppose that manually creating the data directory before running
>> initdb would also avoid this issue, since the mkdir(2) loop is only
>> entered if we don't find the directory in existence.

> Actually, creating the 'data' directory first doesn't work either:

Good point.

> I don't know why the command 'mkdir' doesn't exhibit the
> same problem as the function 'mkdir', but running:

>    mkdir /software/postgresql-8.0.0

> produces the correct error "File exists" on my system.

Could you truss that and see what it does?  It would be a simple change
in initdb to make it stat before mkdir instead of after, but I'm not
totally convinced that would fix the problem.  If mkdir returns a funny
error code then stat might as well ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Kenneth Lareau
Date:
Subject: Re: Strange issue with initdb on 8.0 and Solaris automounts
Next
From: Kenneth Lareau
Date:
Subject: Re: Strange issue with initdb on 8.0 and Solaris automounts