On Tuesday 23 December 2008 16:51:03 Kevin Grittner wrote: > If you look at the serializable queries in the original post for this > thread, it's not hard to see that this standard is not met. The > insert of receipt 3 appears to happen before the update of the control > record, since it has the old deposit date. The transaction which > selects from both tables sees the update to the control record, so it > must come after that. Yet it doesn't see the results of the first > transaction. There is no sequence of serial execution which is > consistent with the behavior.
I am not sure yet whether or not your complaint is valid, but your arguments are not very rigid. Serializability is not defined in terms of what is visible, but what the state of the database is. If you can order the transactions without overlap so that the state of the database is the same as in your original schedule, the schedule is serializable. It is not of concern what was "visible" in between. You may, however, be able to transform that argument to proving that a phantom read is possible, which is how the SQL standard ultimately defines serializability. Also note that discussing what is visible necessarily implies the existence of another transaction that does the reading, and that transaction does not appear to be defined in your arguments. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
