From: Josh Berkus <josh@agliodbs.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
Date: Mon, 2 Feb 2004 21:17:15 -0800
Message-ID: <200402022117.15918.josh@agliodbs.com> (raw)
In-Reply-To: <200402021941.57516.josh@agliodbs.com>
References: <200402020921.12076.josh@agliodbs.com>
<401F0FCD.70903@familyhealth.com.au>
<200402021941.57516.josh@agliodbs.com>
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
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, pgsql-advocacy@postgresql.org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
In-Reply-To: <200402022117.15918.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