Re: [HACKERS] Determine state of cluster (HA)
| От | Joshua D. Drake |
|---|---|
| Тема | Re: [HACKERS] Determine state of cluster (HA) |
| Дата | |
| Msg-id | 2b73583c-eea9-28fc-047d-cd1f3bc1846d@commandprompt.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Determine state of cluster (HA) (Magnus Hagander <magnus@hagander.net>) |
| Список | pgsql-hackers |
On 10/16/2017 03:55 AM, Magnus Hagander wrote: > > > On Mon, Oct 16, 2017 at 4:39 AM, Craig Ringer <craig@2ndquadrant.com > <mailto:craig@2ndquadrant.com>> wrote: > > On 13 October 2017 at 08:50, Joshua D. Drake <jd@commandprompt.com > <mailto: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 Ahh, this is part of the new libpq failover right? Thanks, JD -- Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc PostgreSQL Centered full stack support, consulting and development. Advocate: @amplifypostgres || Learn: https://pgconf.us ***** Unless otherwise stated, opinions are my own. ***** -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: