Re: Separate connection handling from backends - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Separate connection handling from backends
Date
Msg-id a036ec2e-90cf-59a3-0eb0-1880720840d5@BlueTreble.com
Whole thread Raw
In response to Re: Separate connection handling from backends  (Adam Brusselback <adambrusselback@gmail.com>)
List pgsql-hackers
On 12/6/16 1:46 PM, Adam Brusselback wrote:
>     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?

That's a lot more complicated, so I don't see that happening anytime soon.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Partitionning: support for Truncate Table WHERE
Next
From: Ashutosh Bapat
Date:
Subject: Re: Push down more full joins in postgres_fdw