Re: example for read committed/volitile functions

That example is good, except I see the opposite of what the
release notes say.  In 7.4 I see committed transactions from
another session in my function and in 8.0 I do not.

I will go back and verify my tests :(
I don't suppose it is likely that the release notes have
it backwards.  Perhaps I am reading it backwards.

--elein

On Sun, Jan 30, 2005 at 06:51:42PM -0500, Tom Lane wrote:
> elein@varlena.com (elein) writes:
> > I have multiple statements in a READ COMMITTED transaction that
> > can see COMMITs from another concurrent transaction (although not
> > vice versa, of course).  The behaviour is consistent in 7.4 and 8.0
> > and correct imho.
>
> Right, but put those same statements inside a plpgsql function and
> then you'll see a difference.
>
> Essentially, 8.0 causes SQL commands executed inside a function to
> behave the same as they would if issued interactively.  Before, there
> was a difference.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>