don't forget your laptop.
See the links for details:
G+ hackfest event:
https://plus.google.com/u/0/events/cqb5364p4377vd8lp6gvmqqtk6c
DevConf web:
http://www.devconf.cz/
DevConf schedule:
http://developerconference2013.sched.org/
Contact person:
Honza Horak (hho...@redhat.com)
Feel fre
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.
On 06/06/2012 04:50 PM, Andres Freund wrote:
On Wednesday, June 06, 2012 04:38:42 PM Tom Lane wrote:
Florian Pflug writes:
If we're going to have this at all, we should go all the way and
support an arbitrary number of sockets.
Well, that's what I wanted to discuss before Honza starts codi
On 06/06/2012 04:50 PM, Andres Freund wrote:
On Wednesday, June 06, 2012 04:38:42 PM Tom Lane wrote:
You might think we should design this exactly like the TCP-socket
multiple-listen-addresses case, ie just have a config variable
containing a list of directory names. The sticking point there is
On 06/11/2012 11:47 PM, Peter Eisentraut wrote:
On sön, 2012-06-10 at 17:24 -0400, Robert Haas wrote:
and also affects the naming of any UNIX sockets created.
Why would that matter? If you configure M ports and N Unix socket
locations, you get M*N actual sockets created.
...I *seriously* do
On 06/10/2012 12:37 AM, Peter Eisentraut wrote:
On sön, 2012-06-10 at 00:25 +0200, Andres Freund wrote:
We already have the ability to configure the Unix socket
directory in
postgresql.conf. All you need to do is turn that into a list.
That doesn't help libpq using clients.
There is no mand
On 06/10/2012 03:41 PM, Robert Haas wrote:
On Sun, Jun 10, 2012 at 8:36 AM, Tom Lane wrote:
Peter Eisentraut writes:
On lör, 2012-06-09 at 18:26 -0400, Tom Lane wrote:
That's not actually quite the same thing as what I suggest above.
Currently, unix_socket_directory *overrides* the compiled-
On 06/13/2012 03:25 PM, Honza Horak wrote:
Going through the thread, I'd like to sum it up choosing approach with
less potential issues and would like to find a consensus if possible.
It seems unix_socket_directory could be turned into list and probably
renamed to unix_socket_directories,
> On 06/13/2012 03:25 PM, Honza Horak wrote:
> A draft patch is attached. It renames unix_socket_directory to
> unix_socket_directories and allows to use directory:port to be able
> to
> create more sockets in one directory with different port number in
> the
> socket name.
On 06/15/2012 05:40 PM, Honza Horak wrote:
I realized the patch has some difficulties -- namely the socket path in the
data dir lock file, which currently uses one port for socket and the same for
interface. So to allow users to use arbitrary port for all unix sockets, we'd
need t
On 07/02/2012 09:45 PM, Tom Lane wrote:
Honza Horak writes:
On 06/15/2012 05:40 PM, Honza Horak wrote:
I realized the patch has some difficulties -- namely the socket path in the
data dir lock file, which currently uses one port for socket and the same for
interface. So to allow users to
11 matches
Mail list logo
