Re: example for read committed/volitile functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: elein(at)varlena(dot)com (elein)
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: example for read committed/volitile functions
Date: 2005-01-30 23:51:42
Message-ID: 10246.1107129102@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

elein(at)varlena(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-01-31 00:05:13 Re: [pgsql-advocacy] MySQL worm attacks Windows servers
Previous Message Rick Apichairuk 2005-01-30 23:36:54 Re: FreeBSD 5.2.1, postgresql 7.4.5 and shared memory settings