> > 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.
pgsql-hackers by date
|Next:||From: Dominic J. Eidson||Date: 2001-03-30 20:20:17|
|Subject: Re: Re: third call for platforms...|
|Previous:||From: Mikheev, Vadim||Date: 2001-03-30 20:02:34|
|Subject: RE: AW: Re: [SQL] possible row locking bug in 7.0.3 & 7.1 |