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

SR/libpq - outbound interface/ipaddress binding

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: SR/libpq - outbound interface/ipaddress binding
Date: 2010-02-23 09:00:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
While playing with SR/HS in a more complex datacenter environment I 
immediatly hit the need to being able to specify the ipaddress(or 
interface) that the backend(or libpq) uses to connect to the master.

There are a few reasons for being able to do so like:

* we are now suddenly in a situation where the backend can create 
outbound connections on it's own so people will have to add firewall 
rules and being able to guarantee the source IP will help maintainance 
(otherwise stuff might break if you say add an alias IP on an interface)
* prioritising - if you know that replication traffic is on a given IP 
you can actually do fancy stuff like routing it over a different gigE 
line or giving it prority on a WAN connection
* some of those also apply to other libpq clients but those are usually 
not in that complex network/system environments as servers are




pgsql-hackers by date

Next:From: Greg StarkDate: 2010-02-23 09:12:02
Subject: Re: [COMMITTERS] Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
Previous:From: Albe LaurenzDate: 2010-02-23 08:53:00
Subject: Re: Recent vendor SSL renegotiation patches break PostgreSQL

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