On Sat, Jul 09, 2005 at 01:13:13PM +0200, Geert Jansen wrote:
> "Read Committed is the default isolation level in PostgreSQL. When a
> transaction runs on this isolation level, a SELECT query sees only data
> committed before the query began; it never sees either uncommitted data
> or changes c
Geert Jansen <[EMAIL PROTECTED]> writes:
> For my curiosity, what is the reason that in read comitted mode MVCC can
> guarantee a consistent snapshot durign a query, while in serializable
> mode MVCC can guarantee it for a longer interval (the entire
> transaction). Are these different MVCC impl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Fuhr wrote:
>What words in section 12.2.1 are you referring to? I see the
>following (emphasis mine):
>
> In effect, a SELECT query sees a snapshot of the database as of
> the instant that that *query* begins to run. Notice that two
> suc
On Sat, Jul 09, 2005 at 01:18:09PM +0200, Geert Jansen wrote:
>
> The top of section 12.2 of the manual tells that nonrepeatable reads may
> happen in the 'read committed' isolation level. I can understand the
> above behaviour in terms of this. However, the start of section 12.2.1
> tells that in
