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

Re: libpq connectoin redirect

From: feng tian <ft_uw(at)hotmail(dot)com>
To: <lists(at)jwp(dot)name>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq connectoin redirect
Date: 2010-04-22 16:42:06
Message-ID: BAY144-W63D0F0E614A37FDDA973280080@phx.gbl (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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.


> Subject: Re: [HACKERS] libpq connectoin redirect
> From: lists(at)jwp(dot)name
> Date: Wed, 21 Apr 2010 15:52:39 -0700
> CC: pgsql-hackers(at)postgresql(dot)org
> To: ft_uw(at)hotmail(dot)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, instead of accepting the connection, it can reply to client telling it to reconnect to one of the server on  
> ISTM that this would be better handled at a higher-level. That is, given a server ( that holds 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.

In response to

pgsql-hackers by date

Next:From: feng tianDate: 2010-04-22 16:51:12
Subject: Re: libpq connectoin redirect
Previous:From: Robert HaasDate: 2010-04-22 16:20:53
Subject: Re: BETA

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