Re: comparision chart

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: Johannes Grodem <johs(at)copyleft(dot)no>, "p-sql" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: comparision chart
Date: 2002-02-20 08:59:09
Message-ID: GNELIHDDFBOCMGBFGEFOIEHLCBAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> > Widely used as a very fast read only database. Backs _many_ web sites.
> > Locking at the table level only, thus update of the database
> best done when
> > effectively in single-user-mode. Transactions implemented using
> external
> > methods.
>
> The version with InnoDB has row-level locking and transactions. (And
> is supposedly very fast, unlike the BDB-tables.)

I love how they still call it 'mysql' instead of 'sql wrapper around someone
else's better backend library'...

OK, so they have tables with transactions - so now what happens if you do
this?

* begin a transaction
* do a select for update that joins two tables, one with transactions and
one without
* another connection deletes some rows from the transaction-less table out
from under you
* update the transaction-less table
* update the table with transactions
* drop the table with transactions
* rollback the transaction

All sorts of crazy fun!!! It's insane!

(Just my 2c - let's not start another flame war...)

Chris

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Bhuvan A 2002-02-20 12:02:07 combination of 'textcat' and 'interval' in 7.2.
Previous Message Johannes =?iso-8859-15?q?Gr=F8dem?= 2002-02-20 08:36:12 Re: comparision chart