This is a discussion on Re: Strange issue with initdb on 8.0 and Solaris automounts within the pgsql Hackers forums, part of the PostgreSQL category; --> Kenneth Lareau <elessar@numenor.org> writes: > In message <21723.1106868138@sss.pgh.pa.us>, Tom Lane writes: >> I suppose that manually creating the data ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |
| Thread Tools | |
| Display Modes | |
|
|