Re: SSI work for 9.1 - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: SSI work for 9.1
Date
Msg-id 4DF730A5020000250003E5A5@gw.wicourts.gov
Whole thread Raw
In response to Re: SSI work for 9.1  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: SSI work for 9.1
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
> I did some further changes, refactoring SkipSerialization so that
> it's hopefully more readable, and added a comment about the
> side-effects. See attached. Let me know if I'm missing something.
I do think the changes improve readability.  I don't see anything
missing, but there's something we can drop.  Now that you've split
the read and write tests, this part can be dropped from the
SerializationNeededForWrite function:
+
+    /* Check if we have just become "RO-safe". */
+    if (SxactIsROSafe(MySerializableXact))
+    {
+        ReleasePredicateLocks(false);
+        return false;
+    }
If it's doing a write, it can't be a read-only transaction....
-Kevin


pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: Re: patch review : Add ability to constrain backend temporary file space
Next
From: Tom Lane
Date:
Subject: Re: ITYM DROP TABLE