Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-08-02 Thread Dotan Barak
Hi. On Thu, Jul 30, 2009 at 7:33 PM, Tom Lane wrote: > Dotan Barak writes: >> The weird thing is that i used this port in a service that i wrote >> only few seconds before this happened... > > Oh?  How'd you start that service exactly? > > I'm thinking maybe the postmaster inherited the open file

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Tom Lane
Dotan Barak writes: > The weird thing is that i used this port in a service that i wrote > only few seconds before this happened... Oh? How'd you start that service exactly? I'm thinking maybe the postmaster inherited the open file from its parent process. If it's not marked close-on-exec, whi

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Dotan Barak
On Thu, Jul 30, 2009 at 5:33 PM, Tom Lane wrote: > Dotan Barak 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 po

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Tom Lane
Dotan Barak 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? > It seems that the posgres SQL sometimes listen on other ports than 5432: > # lsof -i -n -P | grep postg > postmaste 18415 postgres3

[GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Dotan Barak
Hi. I'm using CentOS 5.3 and PostgreSQL version 8.1.11. I opened the posgres SQL to accept incoming connections: listen_addresses = '*' # comma-separated list of addresses; # defaults to 'localhost', '*' = all port

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Dotan Barak
On Thu, Jul 30, 2009 at 12:14 PM, Richard Huxton wrote: > Dotan Barak wrote: >> >> grep on what? >> (on ps: there isn't anything). > > I was thinking of something like: >  # find /etc -type f -print0 | xargs -0 grep 17583 Thanks for clearing this point; Empty string was found. Dotan -- Sent via

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Richard Huxton
Dotan Barak wrote: grep on what? (on ps: there isn't anything). I was thinking of something like: # find /etc -type f -print0 | xargs -0 grep 17583 -- Richard Huxton Archonet Ltd -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription:

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Dotan Barak
Thanks for the quick response. On Thu, Jul 30, 2009 at 11:26 AM, Richard Huxton 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: >> >> >> listen_addresses = '*' >>                        

Re: [GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Richard Huxton
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: listen_addresses = '*' # comma-separated list of addresses; # defaults to 'localhos

[GENERAL] PostgreSQL server listen on other port than 5432

2009-07-30 Thread Dotan Barak
Hi. I'm using CentOS 5.3 and PostgreSQL version 8.1.11. I opened the posgres SQL to accept incoming connections: listen_addresses = '*' # comma-separated list of addresses; # defaults to 'localhost', '*' = all port =