> You can do that in a more stylish and safer manner by using the
> unix_socket_permissions and unix_socket_group options.

Moving the socket file is also necessary for running in
a chrooted environment.  And I'm not sure whether it's relevant,
but the 7.0 method of computing the socket file name (based
only on the port number) doesn't work for multiple instances
listening on the same port on different IP addresses.

Tue, 14 Nov 2000 13:16:50 -0500 (EST)
djm@web.us.uu.net (David J. MacKenzie)
Re: Re: [PATCHES] PostgreSQL virtual hosting support
djm@web.us.uu.net (David J. MacKenzie) writes:
> but the 7.0 method of computing the socket file name (based
> only on the port number) doesn't work for multiple instances
> listening on the same port on different IP addresses.

I was afraid you were planning to run that way.  Did you absorb the
point about shared memory keys being based (only) on the port number?
Unless something's done about that, the above configuration will NOT
work, because the different instances will try to use the same
shared memory and semaphore sets.

			regards, tom lane

Tue, 14 Nov 2000 13:49:24 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: Re: [PATCHES] PostgreSQL virtual hosting support 