Review: Row-level Locks & SERIALIZABLE transactions,postgres vs. Oracle
in [PgSql]
|
Prev: Review: Row-level Locks & SERIALIZABLE transactions, postgres vs. Oracle
Next: crash-recovery replay of CREATE TABLESPACE isbroken in HEAD
From: Joseph Conway on 17 Jul 2010 15:22 On 7/17/10 12:09 PM, Kevin Grittner wrote: > Joe Conway wrote: > >> Should I be installing Florian's patch in addition to yours when I >> start testing? > > There's some manual fix-up needed, primarily because we need to > differentiate between SERIALIZABLE and REPEATABLE READ isolation > levels, and therefore replaced the IsXactIsoLevelSerializable macro > with IsXactIsoLevelXactSnapshotBased and > IsXactIsoLevelFullySerializable. If you can wait until tomorrow, > I'll create a merged patch for you and confirm that it passes the > modified Florian's pgbench test (with the FOR SHARED clause > removed). I'll include a crude hack to pgbench I had to use to test > this, with an explanation of why it was needed. I'm still trying to > put together better testing techniques for the long term. > >> Also, where can I get the latest and greatest version of your >> patch? > > There's always the git repository, but I'll post a new patch > tomorrow, based on what I've recently found. That all sounds great. I'll concentrate today on understanding the theory and high level design. Joe -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & 24x7 Support -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |