Received: from gauntlet.clinicomp.com (firewall-user@gauntlet.clinicomp.com [209.218.197.226]) by hub.org (8.8.8/8.7.5) with ESMTP id RAA04928 for ; Mon, 14 Sep 1998 17:28:04 -0400 (EDT) Received: by gauntlet.clinicomp.com; id OAA02518; Mon, 14 Sep 1998 14:28:04 -0700 (PDT) Received: from unknown(192.168.101.22) by gauntlet.clinicomp.com via smap (4.1) id xma002504; Mon, 14 Sep 98 14:27:54 -0700 Received: from sgi3 (sgi3 [85.3.1.1]) by proxy.clinicomp.com (8.9.0/8.9.0) with SMTP id OAA27165 for <@proxy.clinicomp.com:pgsql-hackers@postgresql.org>; Mon, 14 Sep 1998 14:27:17 -0700 (PDT) Received: from clinicomp.com by sgi3 via ESMTP (951211.SGI.8.6.12.PATCH1502/940406.SGI) for id OAA23043; Mon, 14 Sep 1998 14:27:59 -0700 Message-ID: <35FD89ED.C1BB3788@clinicomp.com> Date: Mon, 14 Sep 1998 14:26:05 -0700 From: Brian Sanders Organization: CliniComp International X-Mailer: Mozilla 4.04 [en] (WinNT; U) MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Row-level locking Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Are there any plans to add row level locking to Postgres? This is a perfect database for us, but row level locking (or even page level locking) is beginning to become a need for us. Thanks, Brian -- CliniComp, Intl, Inc. ("CCI") does not authorize the use of E- mail messaging to confirm any legally binding contract, agreement, Commitment, representation or warranty. CCI does not assume liability for the content of any E-mail message. Any contract or obligation must be separately confirmed in a document signed (not electronically) by an authorized CCI representative. See CCI's Website at www.clinicomp.com for additional disclaimers, limitations and explanations of CCI's E-mail policies. =