Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when...

From: "Chris Travers" <chris(at)travelamericas(dot)com>
To: "Paul Thomas" <paul(at)tmsl(dot)demon(dot)co(dot)uk>, "pgsql-general (at) postgresql (dot) org" <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 10:52:30
Message-ID: 025001c3b4d4$f8ac6560$2d00053d@SAMUEL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general

HEAP tables in MySQL can be basically used as a network-aware SQL interface
for shared memory segments. I was more looking at the possibility of using
these for coordinating various processes on different systems on a network.

If there is not much performance difference between reasonably small tables
and HEAP tables in MySQL, then I could simply create a simple database and
use that. I was just wondering if there was any other tricks that could be
used, aside from functions written in C ;-)
----- Original Message -----
From: "Paul Thomas" <paul(at)tmsl(dot)demon(dot)co(dot)uk>
To: "pgsql-general @ postgresql . org" <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, November 27, 2003 5:02 PM
Subject: Re: PostgreSQL, MySQL, etc., was Re: [GENERAL] PostgreSQL is much
faster than MySQL, only when...

>
> 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 |
>
+------------------------------+--------------------------------------------
-+
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Jonathan Bartlett 2003-11-27 13:28:32 Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much
Previous Message Paul Thomas 2003-11-27 10:02:08 Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when...

Browse pgsql-general by date

  From Date Subject
Next Message Alex Page 2003-11-27 12:43:04 CREATE TYPE in Postgres 7.3.4
Previous Message Kamil Kukura 2003-11-27 10:24:41 passing function's output into C function