Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA20236 for ; Sun, 1 Aug 1999 10:56:07 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA28388; Sun, 1 Aug 1999 10:55:30 -0400 (EDT) To: "Ross J. Reedstrom" cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] MVCC and concurrent clients In-reply-to: Your message of Sat, 31 Jul 1999 18:05:16 -0500 <19990731180516.A16854@wallace.ece.rice.edu> Date: Sun, 01 Aug 1999 10:55:30 -0400 Message-ID: <28386.933519330@sss.pgh.pa.us> From: Tom Lane "Ross J. Reedstrom" writes: > How about timestamps? I thought about that approach originally, but it doesn't change the nature of the problem. Transactions will not necessarily commit in the same order as the timestamps they've applied to updated tuples. regards, tom lane