Request a Demo
Home   >   mailing lists

Re: could not bind IPv4 socket - Mailing list pgsql-hackers

From Ana Carolina Brito de Almeida
Subject Re: could not bind IPv4 socket
Date
Msg-id 27c6eb60903180820o5834842ct8604409c1f2ad274@mail.gmail.com
Whole thread Raw
In response to could not bind IPv4 socket  (Ana Carolina Brito de Almeida <anacrl@ig.com.br>)
List pgsql-hackers
Tree view
Hi all,

I resolved this problem. I had another postgresql installed and it started automatically when I restarted my computer.

Thanks.

2009/3/18 Ana Carolina Brito de Almeida <anacrl@ig.com.br>
Hi all,

I installed postgresql 8.3.5 with these commands:
- ./configure --enable-thread-safety (I need this because of dbt2)
- make
- make install

I executed initdb. It's ok. I changed "postgresql.conf" file: listen_addresses = '*'.
So, when I started postgresql, I receive these messages:

$ pg_ctl start
server starting
$ LOG:  could not bind IPv4 socket: Address already in use
HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
LOG:  database system was shut down at 2009-03-18 11:32:55 BRT
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections

What's wrong? Why do I receive these messages (about IPv4 socket and HINT)? Can you help me?

Thanks,
Ana Carolina





pgsql-hackers by date:

Previous
From: Ana Carolina Brito de Almeida
Date:
Subject: could not bind IPv4 socket
Next
From: Zdenek Kotala
Date:
Subject: Re: DTrace probes broken in HEAD on Solaris?