Re: Weird behavior with "sensitive" cursors.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Daniel F <dbf13db(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Weird behavior with "sensitive" cursors.
Date: 2009-10-01 20:34:46
Message-ID: 3787.1254429286@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane escribi:
>> I don't think that testing rowMarks is the right thing at all here.
>> That tells you whether it's a SELECT FOR UPDATE, but actually we
>> want any cursor (and only cursors) to have a private snapshot.

> The attached patch implements this. I intend to apply to 8.4 and HEAD
> shortly.

Looks sane. Can we add a short regression test sequence that checks
for this?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-10-01 20:37:05 Re: Vacuumdb Fails: Huge Tuple
Previous Message APseudoUtopia 2009-10-01 20:27:09 Re: Vacuumdb Fails: Huge Tuple