| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(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-07 06:29:34 |
| Message-ID: | a036ec2e-90cf-59a3-0eb0-1880720840d5@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2016-12-07 06:32:35 | Re: Push down more full joins in postgres_fdw |
| Previous Message | Craig Ringer | 2016-12-07 06:26:26 | Re: Partitionning: support for Truncate Table WHERE |