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

From Adam Brusselback
Subject Re: Separate connection handling from backends
Date
Msg-id CAMjNa7dCdgJX4Asj0L+JddL0+Zgqm04DB6JHvjBpw2ALqT25Mg@mail.gmail.com
Whole thread Raw
In response to Re: Separate connection handling from backends  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Separate connection handling from backends  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List 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?

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: WIP: Faster Expression Processing and Tuple Deforming (including JIT)
Next
From: Robert Haas
Date:
Subject: Re: Compiler warnings