Re: SSI work for 9.1

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Dan Ports <drkp(at)csail(dot)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SSI work for 9.1
Date: 2011-06-15 09:10:30
Message-ID: 4DF87706.9030506@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14.06.2011 17:57, Kevin Grittner wrote:
> Heikki Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)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....

Ah, good point. Committed with that removed.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ahmed Shinwari 2011-06-15 09:53:41 [BUG] SSPI authentication fails on Windows when server parameter is localhost or domain name
Previous Message Shigeru Hanada 2011-06-15 08:57:33 Re: per-column generic option