Skip site navigation (1) Skip section navigation (2)

Ability to listen on two unix sockets

From: Honza Horak <hhorak(at)redhat(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Ability to listen on two unix sockets
Date: 2012-06-06 13:50:56
Message-ID: 4FCF6040.5030408@redhat.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

before I ask the main question, just a little background for one issue 
we're currently having in Fedora 17:

PrivateTmp is a systemd's feature, which allows to have private /tmp 
directory for services, which in turn means that such services aren't 
able to access systems's /tmp directory. It's been enabled by some 
services already, including Apache, while PostgreSQL uses system's /tmp 
directory, where its unix socket is located. Naturally, it resulted in a 
state, where Apache or other services with PrivateTmp enabled are not 
able to communicate with PostgreSQL using the socket.

Since we don't want just to move socket for compatibility reasons, I'm 
going to prepare a draft patch to allow PostgreSQL to use a second unix 
socket at a time. A question I'd like to ask now is: Do we need a new 
configuration variable for this or it's enough to have the location 
hard-coded? What are your opinions?

Regards,
Honza

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-06-06 14:11:42
Subject: Re: ExecStoreTuple going into infinite loop
Previous:From: Merlin MoncureDate: 2012-06-06 13:47:33
Subject: Re: ExecStoreTuple going into infinite loop

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group