PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID13793
PG Version9.4.5
OSLinux
Opened2015-12-03 16:55:20+00
Reported byTomasz Torcz
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      13793
Logged by:          Tomasz Torcz
Email address:      (redacted)
PostgreSQL version: 9.4.5
Operating system:   Linux
Description:        

IP_FREEBIND socket option allows application to bind on IP address, which i
s not (yet) configured on any interface. 
I'd like to see Postgresql binding to all specified 'listen_addresses', even
if some of then are not available at the moment pgsql starts.
Optionally, postmaster could put in logs information about that action.
Right know it is:

LOG:  could not bind IPv6 socket: Cannot assign requested address
WARNING:  could not create listen socket for "2001:DB8::1"

It could be:
LOG:  could not bind IPv6 socket: Cannot assign requested address
WARNING:  binding anyway to "2001:DB8::1"





-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Messages

DateAuthorSubject
2015-12-03 16:55:20+00tomek(at)pipebreaker(dot)pl BUG #13793: Please implement IP_FREEBIND option
2018-09-10 13:33:09+00Christoph BergRe: BUG #13793: Please implement IP_FREEBIND option
2018-09-10 13:47:47+00Tom LaneRe: BUG #13793: Please implement IP_FREEBIND option
2018-09-10 14:03:01+00Christoph BergRe: BUG #13793: Please implement IP_FREEBIND option
2018-09-10 14:27:11+00Tomasz TorczRe: BUG #13793: Please implement IP_FREEBIND option
2018-09-10 17:19:19+00Andrew GierthRe: BUG #13793: Please implement IP_FREEBIND option