Re: [HACKERS] READ COMMITTED isolevel is implemented ...

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: t-ishii(at)sra(dot)co(dot)jp
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] READ COMMITTED isolevel is implemented ...
Date: 1999-02-02 10:02:00
Message-ID: 36B6CD18.DF4D6D37@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii wrote:
>
> BTW, what is the advantage of READ COMMMITTED in PostgreSQL? I thought
> the SERIALIZABLE should give us enough concurrency since we are using
> MVCC. Could you give me some examples?

Yes, but UPDATE/DELETE in SERIALIZABLE mode will cause
elog(ERROR, "Can't serialize access due to concurrent update");
in the case of the-same row update.
Oracle sets implicit savepoint before executing a statement.
In Postgres - entire transaction will be aborted...

I have some ideas about savepoints... may be in 6.6 or 6.7...

Vadim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-02-02 10:03:47 Re: [HACKERS] trouble with rules
Previous Message Jan Wieck 1999-02-02 09:54:04 Re: [HACKERS] Small patches in copy.c and trigger.c