From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Dimitri Fontaine" <dimitri(at)2ndquadrant(dot)fr>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Markus Wanner" <markus(at)bluegap(dot)ch>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Issues with Quorum Commit |
Date: | 2010-10-07 19:28:50 |
Message-ID: | 4CADD922020000250003667A@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Establishing an affinity between a session and one of the database
> servers will only help if the traffic is strictly read-only.
Thanks; I now see your point.
In our environment, that's pretty common. Our most heavily used web
app (the one for which we have, at times, needed load balancing)
connects to the database with a read-only login. Many of our web
apps do their writing by posting to queues which are handled at the
appropriate source database later. (I had the opportunity to use
one of these "for real" last night, to fill in a juror questionnaire
after receiving a summons from the jury clerk in the county where I
live.)
Like I said, there are sane cases for this usage, but it won't fit
everybody. I have no idea on percentages.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-10-07 19:31:22 | Re: Git cvsserver serious issue |
Previous Message | Dimitri Fontaine | 2010-10-07 19:26:35 | Re: Issues with Quorum Commit |