| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Keary Suska <hierophant(at)pcisys(dot)net> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Bug or ? |
| Date: | 2005-09-06 00:51:13 |
| Message-ID: | 13090.1125967873@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Keary Suska <hierophant(at)pcisys(dot)net> writes:
> 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.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-06 01:14:48 | Re: Setting up a database for 10000 concurrent users |
| Previous Message | Sergey E. Koposov | 2005-09-06 00:17:54 | Re: Setting up a database for 10000 concurrent users |