On 13 October 2017 at 08:50, Joshua D. Drake <jd@commandprompt.com> wrote: > 5. There is no way to connect to a db node with something akin to > SQL-Server's "application intent" flags, to allow a connection to be > rejected if we wish it to be a read/write connection. This helps detect the > state of the node directly without having to ask any further questions of > the node, and makes it easier to "stall" during connection until a proper > connection can be made.
That sounds desirable, and a good step toward eventually being able to transparently re-route read/write queries from replica to master. Which is where I'd like to land up eventually.
It also sounds a lot like the connection parameter target_session_attrs, does it not? We don't reroute active connections based on it, and we're not smart enough to do anything beyond "try them one by one until you reach the one with the correct attributes", but the basic functionality is there. Basically what we already have fulfills what JD is suggesting, but not what Craig is, if I understand it correctly.
