| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Graham Leggett <minfrin(at)sharp(dot)fm>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Could not create a tablespace - permission denied |
| Date: | 2008-04-19 21:11:02 |
| Message-ID: | 13554.1208639462@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Graham Leggett wrote:
>> - edit /etc/group and add postgres to the group user
> Aha! there it is. Adding a user to a group doesn't mean anything until
> that user reinitializes the environment.
In particular, it looks like the list of groups you belong to is
typically only computed at login time (or equivalently su -l, which
is what's happening in the postgres init script), and then just
inherited by all processes launched from that login. So there is
caching of a sort going on here, but it's in the kernel and there's
nothing we can do about it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phillip Smith | 2008-04-21 00:08:34 | Re: Database update problem from crontab on ubuntu server |
| Previous Message | Joshua D. Drake | 2008-04-19 18:51:53 | Re: Could not create a tablespace - permission denied |