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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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




Browse pgsql-hackers by date

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