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 A5245D1D8A9 for ; Tue, 3 Feb 2004 04:08:54 +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 32152-01 for ; Tue, 3 Feb 2004 00:08:51 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 20C95D1D492 for ; Tue, 3 Feb 2004 00:08:52 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1348ggc011251; Mon, 2 Feb 2004 23:08:42 -0500 (EST) To: josh@agliodbs.com Cc: Christopher Kings-Lynne , Jan Wieck , pgsql-performance@postgresql.org, pgsql-advocacy@postgresql.org Subject: Re: [PERFORM] MySQL+InnoDB vs. PostgreSQL test? In-reply-to: <200402021941.57516.josh@agliodbs.com> References: <200402020921.12076.josh@agliodbs.com> <401EFD98.2020402@Yahoo.com> <401F0FCD.70903@familyhealth.com.au> <200402021941.57516.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Mon, 02 Feb 2004 19:41:57 -0800" Date: Mon, 02 Feb 2004 23:08:42 -0500 Message-ID: <11250.1075781322@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/22 X-Sequence-Number: 3593 Josh Berkus writes: >> Hey at least I noticed that InnoDB has one essential feature we don't: >> SELECT ... IN SHARE MODE; >> >> 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. No, but Chris is correct that we could do with having some kind of shared lock facility at the row level. regards, tom lane