Re: [HACKERS] Bogus path in postmaster.opts

2006-01-19 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> There is another possible answer, and it's something I've been >> meaning to bring up for awhile. Is there a good reason why >> postmaster is a symlink to postgres, rather than a hard link? > I don't know of one. Something I have

Re: [HACKERS] Bogus path in postmaster.opts

2006-01-19 Thread Peter Eisentraut
Tom Lane wrote: > find_my_exec is not misbehaving: it's designed to expand symlinks, > and would in fact be pretty useless if it did not. I don't want to contest that in certain cases this is required but I can easily come up with scenarios (which perhaps no PostgreSQL user has encountered yet)

Re: [HACKERS] Bogus path in postmaster.opts

2006-01-19 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Earlier, CreateOptsFile was called with argv, now it's passed the result of > find_my_exec instead. I'm not sure whether that change was wrong to begin > with or whether find_my_exec is mishaving (it should return something > containing "postmaster

[HACKERS] Bogus path in postmaster.opts

2006-01-19 Thread Peter Eisentraut
Since 8.0, postmaster.opts has been containing .../bin/postgres even though the postmaster was started. This was evidently broken by some Windows-related reshuffling. Earlier, CreateOptsFile was called with argv, now it's passed the result of find_my_exec instead. I'm not sure whether that ch