Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Implement genuine serializable isolation level.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Implement genuine serializable isolation level.
Date: 2011-02-08 03:03:35
Message-ID: AANLkTik8v61EvhMZ3fTzQh2iTYfmtTBqzE8vwkD-Shft@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Mon, Feb 7, 2011 at 5:11 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)iki(dot)fi> wrote:
> Implement genuine serializable isolation level.

With gcc version 4.2.1 (Apple Inc. build 5664):

predicate.c: In function ‘CheckTargetForConflictsIn’:
predicate.c:3674: warning: ‘nexttargettag.locktag_field5’ may be used
uninitialized in this function
predicate.c:3674: warning: ‘nexttargettag.locktag_field4’ may be used
uninitialized in this function
predicate.c:3674: warning: ‘nexttargettag.locktag_field3’ may be used
uninitialized in this function
predicate.c:3674: warning: ‘nexttargettag.locktag_field2’ may be used
uninitialized in this function
predicate.c:3674: warning: ‘nexttargettag.locktag_field1’ may be used
uninitialized in this function

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-02-08 03:05:21
Subject: Re: We need to log aborted autovacuums
Previous:From: Bruce MomjianDate: 2011-02-08 02:51:54
Subject: Re: Why Produce PDF files?

pgsql-committers by date

Next:From: Robert HaasDate: 2011-02-08 03:04:44
Subject: pgsql: Avoid having autovacuum workers wait for relation locks.
Previous:From: Bruce MomjianDate: 2011-02-08 02:51:54
Subject: Re: Why Produce PDF files?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group