From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kenneth Lareau <elessar(at)numenor(dot)org> |
Cc: | "David Parker" <dparker(at)tazznetworks(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Strange issue with initdb on 8.0 and Solaris automounts |
Date: | 2005-01-27 23:50:48 |
Message-ID: | 22095.1106869848@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kenneth Lareau <elessar(at)numenor(dot)org> writes:
> In message <21723(dot)1106868138(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Lareau | 2005-01-28 00:18:36 | Re: Strange issue with initdb on 8.0 and Solaris automounts |
Previous Message | Kenneth Lareau | 2005-01-27 23:35:41 | Re: Strange issue with initdb on 8.0 and Solaris automounts |