From: | "Chris Travers" <chris(at)travelamericas(dot)com> |
---|---|
To: | "Shridhar Daithankar" <shridhar_daithankar(at)myrealbox(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when... |
Date: | 2003-11-27 08:08:14 |
Message-ID: | 022701c3b4bd$c4699be0$2d00053d@SAMUEL |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general |
Hi;
I am trying to determine if there is anything I can do with MySQL that I
can't do with PostgreSQL. HEAP tables are the last one I can't figure out.
HEAP tables are MySQL tables which reside in memory and are visible across
sessions. For obvious reasons, this violates the D in ACID.
In many cases this can be very usefull-- for example if I am building a
system where I want the simplicity of a SQL-like interface with the low
latency of memory-only devices. WOuld I have to run the entire db in a
ramdisk, or can anyone think of a way to do something like this?
It has occurred to me that when table spaces are supported, then this would
be much easier (have a HEAP table space sitting on a ramdisk).
Best WIshes,
Chris Travers
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-11-27 09:18:06 | Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much |
Previous Message | Randolf Richardson | 2003-11-27 07:09:23 | Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when... |
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2003-11-27 08:58:44 | Re: Open source data modeling tools for PostgreSQL |
Previous Message | Thierry Missimilly | 2003-11-27 08:05:38 | Re: What is WAL used for? |