While these can be handled at higher level, for example, by setting
up LDAP or as Hekki suggested, tricking DNS, the problem is that
I don't have control of how the user connect to the server. They
may not use LDAP. Solution like pgbouncer has advantages. User
just get one ip/port and everything else happens automatically.
Thanks,
> Subject: Re: [HACKERS] libpq connectoin redirect
> From: li...@jwp.name
> Date: Wed, 21 Apr 2010 15:52:39 -0700
> CC: pgsql-hackers@postgresql.org
> To: ft...@hotmail.com
>
> On Apr 20, 2010, at 10:03 PM, feng tian wrote:
> > 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.
>
> ISTM that 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. Connect to that server and
> query for the correct target host.
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2
