Re: SSI patch version 12

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <drkp(at)csail(dot)mit(dot)edu>,<heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: <pgsql(at)j-davis(dot)com>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI patch version 12
Date: 2011-01-18 00:52:09
Message-ID: 4D348FD902000025000396E6@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Dan Ports wrote:

> Yes, that comment was supposed to be attached to
> possibleUnsafeConflicts.

> Actually, I think that "other" hash no longer exists

> The comment above SERIALIZABLEXACT also needs to be updated since
> it refers to said hash table. And if I'm not mistaken (Kevin?), we
> can eliminate SERIALIZABLEXACTTAG altogether and not bother putting
> the vxid in the sxact.

I think we still need the vxid. It shows in the pg_locks view, and
we might possibly need it to find the right process to cancel once we
have some way to do that. But there's no point with having the tag
level anymore.

Otherwise, I agree with Dan on all counts.

Dan, if you're not already working on these, I'll take them, so you
can focus on 2PC.

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Urbański 2011-01-18 00:52:58 Re: REVIEW: PL/Python validator function
Previous Message Tomas Vondra 2011-01-18 00:36:59 Re: estimating # of distinct values