Skip site navigation (1) Skip section navigation (2)

Re: MySQL+InnoDB vs. PostgreSQL test?

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: josh(at)agliodbs(dot)com
Cc: pgsql-performance(at)postgresql(dot)org, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?
Date: 2004-02-03 05:52:41
Message-ID: 401F3729.9010202@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-performance
>>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


In response to

pgsql-performance by date

Next:From: Erki KaldjärvDate: 2004-02-03 07:03:05
Subject: Re: inserting large number of rows was: Re: Increasing
Previous:From: Josh BerkusDate: 2004-02-03 05:17:15
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?

pgsql-advocacy by date

Next:From: JeffDate: 2004-02-03 13:52:03
Subject: Re: [PERFORM] MySQL+InnoDB vs. PostgreSQL test?
Previous:From: Josh BerkusDate: 2004-02-03 05:17:15
Subject: Re: MySQL+InnoDB vs. PostgreSQL test?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group