on 9/5/05 6:51 PM, tgl@xxxxxxxxxxxxx purportedly said:
>> FYI, it appears that you cannot start the postmaster when your current
>> working directory is not accessible by the postgres user:
>
> Is there a good reason that this case should work? I don't think it's
> very easy to fix given that we have to resolve the actual location
> of the postmaster executable before we chdir to the data directory.
I'll have to take your word for it as I don't know enough to discuss why/why
not. It's just that this is the first time I have come across an executable
with this particular "restriction".
> In any case, AFAICS this would only be an issue if you do
> "su postgres -c postmaster" rather than "su -l postgres -c postmaster"
> and the former is to be avoided for many reasons besides this one.
I guess this becomes a bug report for the Darwin startup script in contrib,
which is broken not only because it does what you recommend against (above),
but it is also broken in other ways. How does one go about reporting this? I
am not sure who is responsible for contrib stuff.
Thanks,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
