RE: AW: Re: [SQL] possible row locking bug in 7.0.3 & 7 .1 - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: AW: Re: [SQL] possible row locking bug in 7.0.3 & 7 .1
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D3362@sectorbase1.sectorbase.com
Whole thread Raw
List pgsql-hackers
> > This will take thought, research and discussion.  A quick fix is the
> > last thing that should be on our minds.
> 
> From my latest tests( see following post), I tend to agree,
> that this is extremely sensitive :-( 
> I do however think that Vadim's patch description was the
> correct thing to do.

To avoid double tuple versions return - maybe.
To get same results from SELECT and SELECT FOR UPDATE in functions -
no time for 7.1.

> The problem case seems to be when the function is not 
> executed inside a txn.

Any query is executed inside TX. All queries of a function
are executed in the same TX.

Vadim


pgsql-hackers by date:

Previous
From: "Dominic J. Eidson"
Date:
Subject: Re: Re: third call for platforms...
Next
From: "Mikheev, Vadim"
Date:
Subject: RE: 7.1 pg_dump fails for user-defined types (release s topper?)