On Mon, Jan 10, 2011 at 08:49:12AM -0600, Kevin Grittner wrote: > "Kevin Grittner" <kevin.gritt...@wicourts.gov> wrote: > > > In going back through old emails to see what issues might have > > been raised but not yet addressed for the SSI patch, I found the > > subject issue described in a review by Jeff Davis here: > > > > http://archives.postgresql.org/pgsql-hackers/2010-10/msg01159.php > > After reviewing the docs and testing things, I'm convinced that more > work is needed. Because the transaction's writes aren't visible > until COMMIT PREPARED is run, and write-write conflicts are still > causing serialization failures after PREPARE TRANSACTION, some of > the work being done for SSI on PREPARE TRANSACTION needs to be moved > to COMMIT PREPARED. > > It seems likely that shops who use prepared transactions are more > likely than most to care about truly serializable transactions, so I > don't think I should write this off as a limitation for the 9.1 > implementation. Unless someone sees some dire problem with the > patch which I've missed, this seems like my top priority to fix > before cutting a patch.
Could people fix it after the patch? ISTM that a great way to test it is to make very sure it's available ASAP to a wide range of people via the next alpha (or beta, if that's where we're going next). Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers