Re: Unable to start postgresql

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: John Iliffe <john(dot)iliffe(at)iliffe(dot)ca>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unable to start postgresql
Date: 2017-03-09 20:09:58
Message-ID: a306b6ce-0737-88ed-015f-d3b6ded74824@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/09/2017 08:14 AM, John Iliffe wrote:
> On Thursday 09 March 2017 09:17:51 Adrian Klaver wrote:
>> On 03/08/2017 09:28 PM, Tom Lane wrote:
>>> John Iliffe <john(dot)iliffe(at)iliffe(dot)ca> writes:

>
> Comparing my results with Adrian's example, I notice that we both have the
> Unix domain socket 5432 running (1) and we both have an IPv4 and an IPv6
> socket open for postgres (3) and (5) BUT he has a couple of TCP sockets
> that I don't have.(4) and (6) that are assigned specifically to 5442 in his
> case. Shouldn't I have these same lines but assigned to 5432?
>
> I'm assuming that there are two instances of postgresql running on his
> machine (?) on sockets 5432 and 5442 (?).

My mistake, I should have mentioned there are indeed two instances of
Postgres running.

>
> Here is my matching ss output
>
> ------------------------------
> [root(at)prod04 John]# ss -l -p | grep post
> u_str LISTEN 0 128 /tmp/.s.PGSQL.5432 69422 *
> 0 users:(("postgres",pid=2760,fd=5))
> tcp LISTEN 0 128 127.0.0.1:postgres *:*
> users:(("postgres",pid=2760,fd=4))
> tcp LISTEN 0 128 ::1:postgres :::*
> users:(("postgres",pid=2760,fd=3))
> [root(at)prod04 John]#
> ---------------------------------
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Patrick B 2017-03-09 21:01:24 Re: count case when - PG 9.2
Previous Message John Iliffe 2017-03-09 19:51:24 Re: Unable to start postgresql