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 r
[EMAIL PROTECTED] (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 in
On Sun, Jan 30, 2005 at 05:46:03PM -0500, Tom Lane wrote:
> [EMAIL PROTECTED] (elein) writes:
> > I tried to reproduce the case where 7.4 and 8.0 differ
> > on the scope of volitile function with READ COMMITTED
> > transactions.
>
> > In an open transaction in read committed mode.
> > Then I acce
[EMAIL PROTECTED] (elein) writes:
> I tried to reproduce the case where 7.4 and 8.0 differ
> on the scope of volitile function with READ COMMITTED
> transactions.
> In an open transaction in read committed mode.
> Then I access the table and sum columns in a function.
> The results are always c
I tried to reproduce the case where 7.4 and 8.0 differ
on the scope of volitile function with READ COMMITTED
transactions.
In an open transaction in read committed mode.
Then I access the table and sum columns in a function.
The results are always consistent between 7.4 and 8.0
and can see com
