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

Re: PostgreSQL server listen on other port than 5432

From: Dotan Barak <dotanba(at)gmail(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL server listen on other port than 5432
Date: 2009-07-30 09:09:54
Message-ID: 2f3bf9a60907300209g79cfc7yc6c972cf8073c4be@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
Thanks for the quick response.

On Thu, Jul 30, 2009 at 11:26 AM, Richard Huxton<dev(at)archonet(dot)com> wrote:
> Dotan Barak wrote:
>>
>> Hi.
>>
>> I'm using CentOS 5.3 and PostgreSQL version 8.1.11.
>>
>> I opened the posgres SQL to accept incoming connections:
>>
>> <snip start from postgresql.conf>
>> listen_addresses = '*'
>>                                       # comma-separated list of addresses;
>>                                       # defaults to 'localhost', '*' = all
>> port = 5432
>> max_connections = 100
>> <snip end>
>>
>> It seems that the posgres SQL sometimes listen on other ports than 5432:
>> # lsof -i -n -P  | grep postg
>> postmaste 18415 postgres    3u  IPv4  99670       TCP *:17583 (LISTEN)
>> postmaste 18415 postgres    4u  IPv6 102029       TCP *:5432 (LISTEN)
>> postmaste 18415 postgres    5u  IPv4 102030       TCP *:5432 (LISTEN)
>
> Never seen this before. One thing that does leap out though is that you've
> got IPv4 and IPv6 sockets active at the same time. Does grepping for "17583"
> show anything useful?

grep on what?
(on ps: there isn't anything).

Dotan

In response to

Responses

pgsql-general by date

Next:From: Richard HuxtonDate: 2009-07-30 09:14:38
Subject: Re: PostgreSQL server listen on other port than 5432
Previous:From: Greg StarkDate: 2009-07-30 09:02:44
Subject: Re: Clients disconnect but query still runs

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