| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | <simon(at)2ndQuadrant(dot)com>,<markus(at)bluegap(dot)ch>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SSI patch version 14 |
| Date: | 2011-02-06 05:40:23 |
| Message-ID: | 4D4DDFE7020000250003A492@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" wrote:
> So now that I'm sure we actually do need code there, I'll add it.
Hmmm... First cut at this here:
http://git.postgresql.org/gitweb?p=users/kgrittn/postgres.git;a=commitdiff;h=3ccedeb451ee74ee78ef70735782f3550b621eeb
It passes all the usual regression tests, the new isolation tests,
and the example posted earlier in the thread of a test case which was
allowing an anomaly. (That is to say, the anomaly is now prevented.)
I didn't get timings, but it *seems* noticeably slower; hopefully
that's either subjective or fixable. Any feedback on whether this
seems a sane approach to the issue is welcome.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2011-02-06 06:41:25 | Range Types |
| Previous Message | Robert Haas | 2011-02-06 00:54:42 | Re: [COMMITTERS] pgsql: Include more status information in walsender results |