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

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 (view raw or flat)
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

pgsql-hackers by date

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

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