snapshots

From: Kovacs Baldvin <kb136(at)hszk(dot)bme(dot)hu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: snapshots
Date: 2001-02-04 16:03:54
Message-ID: Pine.GSO.4.21.0102041649350.16577-100000@ural2
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello.

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.

A few lines in src/backend/tcop/pquery.c runs when
a DECLARE cursor is issued:

> if (isRetrieveIntoPortal)
> {
> PortalExecutorHeapMemory = NULL;
>
> ProcessPortal(intoName,
> [...]
> return;
> }

, but I cannot see neither in these, nor in ProcessPortal that
where does it fix the set of rows being visible.

Please help to find it out.

Thanks,
Baldvin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kajetan Hofman 2001-02-04 16:28:53 Getting Software
Previous Message Kovacs Baldvin 2001-02-04 15:49:31 Message of MOVE