Re: [HACKERS] Client Connection redirection support for PostgreSQL

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Client Connection redirection support for PostgreSQL
Date: 2018-10-02 03:00:51
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Jul 13, 2018 at 04:20:15PM -0400, Dave Cramer wrote:
> However it would be far better to have a startup parameter which indicated
> that we wanted to connect to a read only database. At that point
> pools could redirect to a secondary. Given the proliferation of cloud based
> implementations I can see this being a useful feature.

The thread has died here... Without any input from the author for many
months. So I am marking it as returned with feedback.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2018-10-02 03:42:59 Re: SerializeParamList vs machines with strict alignment
Previous Message Michael Paquier 2018-10-02 02:58:41 Re: [HACKERS] [PATCH] Overestimated filter cost and its mitigation