Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] MVCC works in serialized mode!

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] MVCC works in serialized mode!
Date: 1998-12-25 10:32:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> 2. LOCK TABLE modes are not yet implemented...

Implemented, as well as SET TRANSACTION ISOLATION LEVEL...

> 3. As well as SELECT ... FOR UPDATE: I need in advice here!
>    Do Oracle, Informix etc support SELECT FOR UPDATE if
>    there are aggregates, group by, distinct in SELECT ???

As I see in Oracle documentation FOR UPDATE is disallowed
in these cases... No objections ?

>    Is SELECT FOR UPDATE allowed in subqueries ???

Could someone test this?

> 7. As I read in Sybase documentation the default
>    standard transaction mode is _chained_ - all
>    queries before explicit COMMIT/ABORT are run in _single
>    transaction_... But we have to use BEGIN/END to get it!
>    This was not so bad for system with relation level locks,
>    but now only the same row writes block one other and so
>    chained mode seems more appropriate...
>    Shouldn't we change default transaction mode now?
>    And use option/SET TRANSACTION MODE to switch to
>    un-chained mode if one like it?

No comments on this?
I would like to make BEGIN implicit...


In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-12-25 11:22:01
Subject: Re: [HACKERS] postgresql-6.4.1.tar.gz
Previous:From: Edmund MerglDate: 1998-12-25 08:35:13
Subject: postgresql-6.4.1.tar.gz

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group