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

Re: Occupied port warning

From: Abhijit Menon-Sen <ams(at)oryx(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: andrew(at)dunslane(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Occupied port warning
Date: 2005-06-28 13:40:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
At 2005-06-28 15:14:29 +0200, peter_e(at)gmx(dot)net wrote:
> I recall that it had something to do with IPv6, but I'm not sure.

Under Linux, if you bind to AF_INET6/::0, a subsequent bind to AF_INET/0
will fail, but the IPv4 address is also bound by the first call, and the
program will accept IPv4 connections anyway (BSD behaves differently).

Maybe that had something to do with it? I remember I had to add code to
my program to allow that second bind to fail without complaint, and now
my code also exits only if it can't bind anything at all.

(For what it's worth, I don't think this behaviour is such a big deal.)

-- ams

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-06-28 13:51:20
Subject: Re: Implementing SQL/PSM for PG 8.2 - debugger
Previous:From: Pavel StehuleDate: 2005-06-28 13:19:12
Subject: Re: Implementing SQL/PSM for PG 8.2 - debugger

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