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; --> In message <22687.1106872653@sss.pgh.pa.us>, Tom Lane writes: >Kenneth Lareau <elessar@numenor.org> writes: >> In message <22095.1106869848@sss.pgh.pa.us>, Tom Lane writes: >>> Could ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In message <22687.1106872653@sss.pgh.pa.us>, Tom Lane writes: >Kenneth Lareau <elessar@numenor.org> writes: >> In message <22095.1106869848@sss.pgh.pa.us>, Tom Lane writes: >>> Could you truss that and see what it does? > >> Here's the relevant truss output from 'mkdir /software/postgresql-8.0.0' >> on my Solaris 9 system: > >> 10832: mkdir("/software/postgresql-8.0.0", 0777) Err#89 ENOSYS >> 10832: stat64("/software/postgresql-8.0.0", 0xFFBFFA38) = 0 > >> It's doing the stat after the mkdir attempt it seems, and coming back >> with the correct response. Hmm, maybe I should look at the Solaris 8 >> code for the mkdir command... > >Well, the important point is that the stat does succeed. I'm not going >to put in anything as specific as a check for ENOSYS, but it seems >reasonable to try the stat first and mkdir only if stat fails. >I've applied the attached patch. > > regards, tom lane Tom, thank you very much for the patch, it worked like a charm. Ken Lareau elessar@numenor.org ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|