Received: from uno.tksoft.com (modem-17.copernicus.brandx.net [209.55.65.17]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA40117 for ; Mon, 2 Aug 1999 18:34:48 -0400 (EDT) (envelope-from tk@uno.tksoft.com) Received: (from tk@localhost) by uno.tksoft.com (8.8.8/8.8.8) id NAA15844; Mon, 2 Aug 1999 13:44:25 -0700 From: "tjk@tksoft.com" Message-Id: <199908022044.NAA15844@uno.tksoft.com> Subject: Re: [SQL] MVCC and concurrent clients To: tgl@sss.pgh.pa.us (Tom Lane) Date: Mon, 2 Aug 1999 13:44:25 -0700 (PDT) Cc: pgsql-sql@postgreSQL.org In-Reply-To: <28386.933519330@sss.pgh.pa.us> from "Tom Lane" at Aug 1, 99 10:55:30 am Content-Type: text Tom, I missed a part of this dialogue, but if I am correct we are talking about problems associated with concurrent updates. Since this is such an important topic, how about creating a description of the specific problems associated with the issue, with the goal of establishing a comprehensive solution(s) to handle the different needs of various client programs? My thought would be to have a serial number which can be requested from the server for updates, so that applications which must/want to process updates sequentially can do so. (updates=updates/deletes/inserts) Troy Troy Korjuslommi Tksoft OY, Inc. tjk@tksoft.com Software Development Open Source Solutions Hosting Services