From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | felix(at)crowfix(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Gentoo, 8,2 ---> 8.4, and /var/run/postgresql in mode 770 |
Date: | 2010-01-09 21:57:47 |
Message-ID: | dcc563d11001091357k5d50633fxe479729ec7fad6ab@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jan 9, 2010 at 2:20 PM, <felix(at)crowfix(dot)com> wrote:
> I just upgraded my home gentoo system's postgresql from 8.2.14 to
> 8.4.2. I use it mostly for fooling around and keeping smatterings of
> personal data, so it was simple laziness which kept me from upgrading
> sooner, triggered by the gentoo switch back in 8.2.mumble in how they
> manage postgresql.
>
> Everything went smoothly except the permissions of the directory
> /var/run/postgresql with the domain socket .s.PGSQL.5432. This dir
> had permissions of 770, owned by postgres.postgres, so no mere mortals
> could access it. I have changed this to 775 and can now access it.
>
> Didn't 8.2 put these in /tmp? Maybe this was a gentoo thing. What
> should the permissions be for this? Or does gentoo do their own thing
> and there is a different "standard" way of handling this?
This sounds like a Gentoo thing. The location of all the various pg
files is a compile time option and lots of packagers make different
decisions based on their distro layouts. Ubuntu / Debian for instance
puts all the postgresql.conf type files in
/etc/postgresql/8.x/<clustername>/ and allows you to have multiple
instances of different versions by moving things around from the
default of a single pg install from source.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-01-09 21:58:55 | Re: An issue with max() and order by ... limit 1 in postgresql8.3-beta3 |
Previous Message | Dimitri Fontaine | 2010-01-09 21:50:53 | Re: dynamic insert in plpgsql |