Re: "serializable" in comments and names - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: "serializable" in comments and names
Date
Msg-id 1283963981-sup-9057@alvh.no-ip.org
Whole thread Raw
In response to Re: "serializable" in comments and names  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "serializable" in comments and names  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Excerpts from Tom Lane's message of mié sep 08 12:12:31 -0400 2010:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Excerpts from Kevin Grittner's message of vie sep 03 19:06:17 -0400 2010:
> >>> How about IsolationUsesXactSnapshot
> 
> > I find this name confusing :-(  Doesn't a READ COMMITTED transaction use
> > transaction snapshots as well?
> 
> AFAIR it doesn't keep the first snapshot around.  If it did, most of
> your work on snapshot list trimming would have been useless, no?

That's my point precisely.  The name "IsolationUsesXactSnapshot" makes
it sound like it applies to any transaction that uses snapshots for
isolation, doesn't it?  How about IsolationUses1stXactSnapshot, or
something else that makes it clearer that there's a difference between
that and read committed transactions?

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plan time of MASSIVE partitioning ...
Next
From: Bruce Momjian
Date:
Subject: Re: "serializable" in comments and names