From: | Kevin Grittner <grimkg(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, Florian Pflug <fgp(at)phlo(dot)org> |
Subject: | Re: Review: Row-level Locks & SERIALIZABLE transactions, postgres vs. Oracle |
Date: | 2010-09-18 18:44:48 |
Message-ID: | AANLkTimvxr1SaR-N6x_Q2gouLp=OttjYdctxn5MUDc-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
This patch suffered a lot of bitrot in the last month, mostly due to the
noop patch for SSI. It also used the term SERIALIZABLE in many places to
indicate any transaction-snapshot mode transaction, so I applied changes
consistent with the noop patch. I also found a few whitespace and brace
usage issues which seemed to conflict with conventional usage and cleaned
those up. A minor spelling typo also corrected.
A new patch reflecting all this is attached.
This now compiles and passes regression tests. I still need to re-run all
the other tests which Florian and I previously used to test the patch. I
don't have any reason to expect that they will now fail, but one need to be
thorough. Once that is confirmed, I think this will be ready for committer
unless someone can think of something else to throw at it first.
-Kevin
Attachment | Content-Type | Size |
---|---|---|
serializable_row_locks-v2.patch | text/x-diff | 52.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-09-18 18:52:29 | Re: Serializable Snapshot Isolation |
Previous Message | Tom Lane | 2010-09-18 18:41:33 | Re: INSERT and parentheses |