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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL server listen on other port than 5432
Date: 2009-07-30 15:46:04
Message-ID: 2f3bf9a60907300846n4042b13ave0fea7d47e09c45@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Thu, Jul 30, 2009 at 5:33 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dotan Barak <dotanba(at)gmail(dot)com> writes:
>> I'm using CentOS 5.3 and PostgreSQL version 8.1.11.
>
> Are you using the Red Hat/CentOS postgresql RPMs, or some other
> distribution of PG?
Yes, I'm using the original RPM that comes with CentOS.

>
>> 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)
>
> Odd, particularly seeing that that port was evidently opened before
> 5432.  The only idea that comes to mind is that it's being opened by
> a library for Kerberos or LDAP or some such.  What auth methods have
> you got listed in pg_hba.conf?
>
>                        regards, tom lane
>
"trust all".


The weird thing is that i used this port in a service that i wrote
only few seconds before this happened...

Dotan

In response to

Responses

pgsql-general by date

Next:From: Emanuel Calvo FrancoDate: 2009-07-30 16:09:09
Subject: Re: Problems compiling contribs in Open Solaris
Previous:From: Chris BrowneDate: 2009-07-30 15:45:19
Subject: Re: SVN and Postgres 8.3

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