Re: Separate connection handling from backends

From: Adam Brusselback <adambrusselback(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)ymail(dot)com>
Subject: Re: Separate connection handling from backends
Date: 2016-12-06 21:46:28
Message-ID: CAMjNa7dCdgJX4Asj0L+JddL0+Zgqm04DB6JHvjBpw2ALqT25Mg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> BTW, it just occurred to me that having this separation would make it
> relatively easy to support re-directing DML queries from a replica to the
> master; if the backend throws the error indicating you tried to write data,
> the connection layer could re-route that.

This also sounds like it would potentially allow re-routing the other way
where you know the replica contains up-to-date data, couldn't you
potentially re-direct read only queries to your replicas?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joseph Brenner 2016-12-06 21:53:08 Re: Select works only when connected from login postgres
Previous Message Peter Geoghegan 2016-12-06 21:27:14 Re: WIP: Faster Expression Processing and Tuple Deforming (including JIT)