Re: storage engine , mysql syntax CREATE TABLE t (i INT)

From: "Scott Marlowe" <smarlowe(at)qwest(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Gaetano Mendola" <mendola(at)bigfoot(dot)com>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: storage engine , mysql syntax CREATE TABLE t (i INT)
Date: 2004-07-26 04:55:49
Message-ID: 1090817749.22512.1.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 2004-07-25 at 22:23, Tom Lane wrote:
> I don't think
> it's either practical or interesting to try to introduce an equivalent
> layering into Postgres.

I can possibly see a use for a row locking storage system, i.e. non MVCC
for some applications. But I can't see it being worth the amount of
work it would require.

Or is the locking model too high level to be handled this way? Just
wondering.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-26 04:57:03 Re: CVS web interface error
Previous Message Gavin Sherry 2004-07-26 04:51:14 Re: storage engine , mysql syntax CREATE TABLE t (i INT)