Re: libpq connectoin redirect

While these can be handled at higher level, for example, by setting <br />up LDAP or as Hekki suggested, tricking DNS,
theproblem is that <br />I don't have control of how the user connect to the server.  They <br />may not use LDAP. 
Solutionlike pgbouncer has advantages.  User<br />just get one ip/port and everything else happens automatically.<br
/><br/>Thanks,<br /><br /><br />> Subject: Re: [HACKERS] libpq connectoin redirect<br />> From: lists@jwp.name<br
/>>Date: Wed, 21 Apr 2010 15:52:39 -0700<br />> CC: pgsql-hackers@postgresql.org<br />> To:
ft_uw@hotmail.com<br/>> <br />> On Apr 20, 2010, at 10:03 PM, feng tian wrote:<br />> > Another way to do
this,is to send the client an "redirect" message. When client connect to 127.0.0.10, instead of accepting the
connection,it can reply to client telling it to reconnect to one of the server on 127.0.0.11-14. <br />> <br />>
ISTMthat this would be better handled at a higher-level. That is, given a server (127.0.0.10) that holds 127.0.0.11-14.
Connectto that server and query for the correct target host.<br /><br /><hr />Hotmail is redefining busy with tools for
theNew Busy. Get more from your inbox. <a
href="http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2"
target="_new">Seehow.</a>