From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | drkp(at)csail(dot)mit(dot)edu, heikki(dot)linnakangas(at)enterprisedb(dot)com, pgsql(at)j-davis(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SSI patch version 12 |
Date: | 2011-01-18 05:09:32 |
Message-ID: | 29513.1295327372@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Dan Ports wrote:
> .... The biggest, in my mind, is whether
> MySerializableXact needs to be declared volatile.
> The problem is that I don't have a very clear sense of what it really
> does, which is not helped much by having done a few years of Java
> programming, where the same keyword seems to have a vaguely-similar-
> but-not-really-the-same meaning.
In C it means that the compiler must not try to optimize away loads or
stores of the variable, because the variable is subject to being read or
changed by outside forces (interrupt service routines, other processes
or threads, etc).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2011-01-18 05:15:59 | Confusing comment in TransactionIdIsInProgress |
Previous Message | Tom Lane | 2011-01-18 05:04:00 | Re: pg_filedump moved to pgfoundry |