Re: pg_ctl and port number detection

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Florian Pflug <fgp(at)phlo(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_ctl and port number detection
Date: 2010-12-21 02:43:06
Message-ID: 201012210243.oBL2h6L18345@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian Pflug wrote:
> On Dec21, 2010, at 03:04 , Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Actually, if we're going to do this at all, we should do
> >>
> >> pid
> >> datadir
> >> port
> >> socketdir
> >> ... here be dragons ...
> >>
> >> so that pg_ctl doesn't have to assume the server is running with a
> >> default value of unix_socket_dir. Not sure what to put in the fourth
> >> line on Windows though ... maybe just leave it empty?
> >
> > I am curious about the use of the socketdir. What can that be used for?
>
> If it's non-default and you want to connect via unix sockets, just knowing
> the port won't help much.

Ah, so pg_ctl is going to use that information too --- good point!

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomáš Mudruňka 2010-12-21 05:29:38 [FeatureRequest] Base Convert Function
Previous Message Florian Pflug 2010-12-21 02:30:28 Re: pg_ctl and port number detection