Re: postgreslog - panic message

On May 25 11:04, Richard Huxton wrote:
> surabhi.ahuja wrote:
> >hi,
> >i am getting the following error messages:
> >
> ><2006-05-24 15:28:08 CDT%>LOG:  could not bind IPv4 socket: Address
> >already in use
> ><2006-05-24 15:28:08 CDT%>HINT:  Is another postmaster already running on
> >port 5432? If not, wait a few seconds and retry.
> ><2006-05-24 15:28:08 CDT%>WARNING:  could not create listen socket for
> >"localhost"
> ><2006-05-24 15:28:08 CDT%>LOG:  database system was shut down at
> >2006-05-24 15:28:08 CDT
>
> This is what it says. You've either got:
> 1. another version of PostgreSQL running on port 5432
> 2. Something else on port 5432
> 3. The operating-system hasn't recycled the port after a shutdown (it
> can take a few seconds sometimes).

Just for curiosity, shouldn't SO_REUSEADDR (in
backend/libpq/pqcomm.c:342) handle the 3rd possibility in the above
list? Or isn't this behaviour guaranteed by SO_REUSEADDR on every
platform?


Regards.