Re: incoherent view of serializable transactions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: incoherent view of serializable transactions
Date: 2008-12-29 15:27:51
Message-ID: 49589817.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Serializability is not defined in terms of what is visible, but what
the
> state of the database is.

A belated thought on this: It would be easy enough to add a
daily_receipt_total table to the example to capture the result of the
query, instead of assuming that it merely prints on the daily bank
deposit report. That would certainly meet your test of ending with an
invalid database state after all the transactions commit.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aidan Van Dyk 2008-12-29 15:51:40 Re: Several tags around PostgreSQL 7.1 broken
Previous Message Kevin Grittner 2008-12-29 15:16:42 Re: incoherent view of serializable transactions