Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!caen!spool.mu.edu!agate!eden.Berkeley.EDU!mao
From: mao@eden.Berkeley.EDU (Mike Olson)
Newsgroups: comp.databases
Subject: Re: Oracle CURSORS useless ?
Message-ID: <1991Jun27.225555.27108@agate.berkeley.edu>
Date: 27 Jun 91 22:55:55 GMT
References: <1991Jun26.033043.22948@sunaus.oz> <25731@well.sf.ca.us>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California at Berkeley
Lines: 14

In <25731@well.sf.ca.us>, gatynen@well.sf.ca.us (Gerard Tynen) writes

> We couldn't think of any reason to force a close on all cursors just
> because you do a commit.

if you're doing two-phase locking, and you release locks at commit time,
you'd better close your cursors.  changes by concurrent transactions will
become visible at that time, too, which means that the set of prefetched
values cached in the cursor may be wrong if you keep it open.

					mike olson
					postgres research group
					uc berkeley
					mao@postgres.berkeley.edu