Re: snapshots - Mailing list pgsql-hackers

From Tom Lane
Subject Re: snapshots
Date
Msg-id 6834.981315242@sss.pgh.pa.us
Whole thread Raw
In response to snapshots  (Kovacs Baldvin <kb136@hszk.bme.hu>)
List pgsql-hackers
Kovacs Baldvin <kb136@hszk.bme.hu> writes:
> Could somebody explain me the mechanism in the backend,
> which is responsible for the followings. (I tried to
> look around snapshots, but couldnt figure out th answer).

> In a transaction, isol. read comitted, a select from a
> table can see the comitted changes by others, but
> a previously declared cursor can not.

Yup.  The snapshot used for a particular query is nailed down when
ExecutorStart() is called.  Look around for uses of QuerySnapshot
and estate->es_snapshot.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: [PATCHES] A Sparc/Linux patch (for 7.1), and a Linux rc.d/init.d script....
Next
From: Peter Eisentraut
Date:
Subject: Re: [BUGS] syslog logging setup broken?