X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CD1A8D1CCD6; Tue, 3 Feb 2004 05:18:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 45848-10; Tue, 3 Feb 2004 01:18:10 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id A58F7D1CAF6; Tue, 3 Feb 2004 01:18:10 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 4361698; Mon, 02 Feb 2004 21:19:13 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Christopher Kings-Lynne Subject: Re: MySQL+InnoDB vs. PostgreSQL test? Date: Mon, 2 Feb 2004 21:17:15 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org, pgsql-advocacy@postgresql.org References: <200402020921.12076.josh@agliodbs.com> <401F0FCD.70903@familyhealth.com.au> <200402021941.57516.josh@agliodbs.com> In-Reply-To: <200402021941.57516.josh@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402022117.15918.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/12 X-Sequence-Number: 3583 Chris, > > Which does a shared lock on a row as opposed to a write lock, hence > > avoiding nasty foreign key deadlocks... > > Um, wrong. We don't lock rows for SELECT. Unless you meant something else? Am I not following you? -- -Josh Berkus Aglio Database Solutions San Francisco