From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 19:40:46 |
Message-ID: | 20091001194046.GJ5607@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane escribió:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Tom Lane escribió:
> >> Well, the first problem is that 8.4 is failing to duplicate the
> >> historical behavior.
>
> > Oh! That's easy.
>
> 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.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Attachment | Content-Type | Size |
---|---|---|
snapmgr-bugfix-2.patch | text/x-diff | 3.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-10-01 20:21:00 | Re: Vacuumdb Fails: Huge Tuple |
Previous Message | APseudoUtopia | 2009-10-01 19:12:01 | Re: Vacuumdb Fails: Huge Tuple |