From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Comments from a Firebird user via Borland Newsgroups. |
Date: | 2005-11-10 01:50:39 |
Message-ID: | 1131587439.819.72.camel@home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2005-11-09 at 19:35 -0600, Tony Caduto wrote:
> <We found PostgreSQL a mature product, but in two things Firebird was
> simply better than PostgreSQL: Two-Phase commit (ok, that is gone with
> PG 8.1), but the second is a SNAPSHOT / REPEATABLE READ transaction
> isolation. I can't live without that when it comes having a stable view
> of data during one transaction, or did that change with 8.1? Is there
> now a SNAPHOST / REPEATBLE READ transaction isolation level available as
> well?>
>
> Just wondering what the PG take on this snapshot repeatable read stuff is.
It has kinda been there for years and is what PostgreSQL uses to achieve
a consistent snapshot with pg_dump. Of course, per spec the DB is
allowed to upgrade the isolation level to SERIALIZABLE from what you
specify you require as a minimum (REPEATABLE READ in this case).
session1:
begin isolation level repeatable read;
session2:
insert into junk values (1);
session1:
rbt=# select * from junk;
col
-----
1
(1 row)
session2:
insert into junk values (2);
session1:
rbt=# select * from junk;
col
-----
1
(1 row)
--
From | Date | Subject | |
---|---|---|---|
Next Message | User Chriskl | 2005-11-10 02:06:46 | dbsamples - dbsamples: Imported Sources |
Previous Message | ITAGAKI Takahiro | 2005-11-10 01:42:53 | Re: Optimization of the alignment padding |