On 27/11/2003 08:08 Chris Travers wrote:
> 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).
If your table is that small, you could just cache it in your application.
--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller
Business |
| Computer Consultants |
http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+---------------------------------------------+