On Thu, Nov 2, 2017 at 4:33 PM, Craig Ringer wrote:
>> Add the ability to the PostgreSQL server instance to route the traffic to a
>> different server instance based on the rules defined in server’s pg_bha.conf
>> configuration file. At a high level this enables offloading
> pg_hba.conf is "host based access [control]" . I'm not sure it's really the
> right place.
I am open to have another configuration file, say routing_list.conf to define
the routing rules, but felt it is easy to extend the hba conf file.
> But we now have a session-intent stuff though. So we
> What advantages do you see in doing this in the backend over the current
> system where the concerns are separated, i.e. people use connection poolers
> like pgbouncer to do the routing?
IMHO connection pooler is not great for latency sensitive applications. For
small deployments, proxy is
On 2 November 2017 at 14:02, Satyanarayana Narlapuram
wrote:
> Proposal:
>
> Add the ability to the PostgreSQL server instance to route the traffic to a
> different server instance based on the rules defined in server’s pg_bha.conf
> configuration file. At
On Thu, Nov 02, 2017 at 06:02:43AM +, Satyanarayana Narlapuram wrote:
> Proposal:
> Add the ability to the PostgreSQL server instance to route the
> traffic to a different server instance based on the rules defined in
> server's pg_bha.conf configuration file. At a high level this
> enables
Proposal:
Add the ability to the PostgreSQL server instance to route the traffic to a
different server instance based on the rules defined in server's pg_bha.conf
configuration file. At a high level this enables offloading the user requests
to a different server instance based on the rules