From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
Date: Tue, 03 Feb 2004 13:52:41 +0800
Message-ID: <401F3729.9010202@familyhealth.com.au> (raw)
In-Reply-To: <200402022117.15918.josh@agliodbs.com>
References: <200402020921.12076.josh@agliodbs.com>
<401F0FCD.70903@familyhealth.com.au>
<200402021941.57516.josh@agliodbs.com>
<200402022117.15918.josh@agliodbs.com>
>>Um, wrong. We don't lock rows for SELECT.
>
> Unless you meant something else? Am I not following you?
I mean row level shared read lock. eg. a lock that says, you can read
but you cannot delete.
It's what postgres needs to alleviate its foreign key trigger deadlock
problems.
Chris
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: chriskl@familyhealth.com.au, josh@agliodbs.com, pgsql-advocacy@postgresql.org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
In-Reply-To: <401F3729.9010202@familyhealth.com.au>
References: <200402020921.12076.josh@agliodbs.com> <401F0FCD.70903@familyhealth.com.au> <200402021941.57516.josh@agliodbs.com> <200402022117.15918.josh@agliodbs.com> <401F3729.9010202@familyhealth.com.au>
* 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