Re: Client Connection redirection support for PostgreSQL

From: Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Client Connection redirection support for PostgreSQL
Date: 2017-11-03 06:40:59
Message-ID: CY1PR21MB0024E95AD80EF5562D7D22E5915D0@CY1PR21MB0024.namprd21.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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 could possibly do it at session level.
Session intent can be used as an obvious hint for the routing to kick in. This can be a rule in the routing list to route the read intent sessions round robin across multiple secondary replicas.

> Backends used just for a redirect would be pretty expensive though.
It is somewhat expensive as the new process fork has to happen for each new connection. The advantage is that it makes proxies optional (if the middle tier can do connection management), and all the routing configurations can be within the server.
This also benefits latency sensitive applications not going through proxy.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-11-03 07:20:15 Re: How to implement a SP-GiST index as a extension module?
Previous Message Satyanarayana Narlapuram 2017-11-03 06:31:18 Re: Client Connection redirection support for PostgreSQL