From: Josh Berkus <josh@agliodbs.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
Date: Mon, 2 Feb 2004 19:41:57 -0800
Message-ID: <200402021941.57516.josh@agliodbs.com> (raw)
In-Reply-To: <401F0FCD.70903@familyhealth.com.au>
References: <200402020921.12076.josh@agliodbs.com>
<401EFD98.2020402@Yahoo.com>
<401F0FCD.70903@familyhealth.com.au>
Chris,
> 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.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, chriskl@familyhealth.com.au, JanWieck@Yahoo.com, pgsql-advocacy@postgresql.org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
In-Reply-To: <200402021941.57516.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox