From: | "John P(dot) Looney" <john(at)antefacto(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Embedded postgres ? |
Date: | 2001-10-15 17:29:08 |
Message-ID: | 20011015182908.B1539@antefacto.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Oct 11, 2001 at 09:08:51AM -0400, Henning Follmann mentioned:
> > I don't know it's architecture too well, though even with a very small
> > database, it seems to use a huge number of files, which are all quite
> > large, for the small amount of information in it.
> Well, this is not for what postgres was designed for.
> For embedded systems you are looking for databases that are optimised
> for running completely in memory. Also a SQL engine is maybe not well
> suited for embedded devices.
Well, these days "embedded" means a lot more than 64k of RAM...
I was hoping to be able to run a full RDBMS from a RAM disk. Though,
postgres seems to have the strange idea of a new file for each update.
This seems to chew through disk space.
As well as tuning for massive systems, can you tune it to a small system?
> Better would be databases like Berley DB or GDBM. They are though not
> comparable to RDBMS like postgres, etc...
Indeed. We are using TDB at the moment; nice, small...but it doesn't
quite support joins or triggers :)
John
--
_______________________________________
John Looney Chief Scientist
a n t e f a c t o t: +353 1 8586004
www.antefacto.com f: +353 1 8586014
From | Date | Subject | |
---|---|---|---|
Next Message | roypgsqlgen | 2001-10-15 18:13:14 | |
Previous Message | Andrew Gould | 2001-10-15 17:14:58 | Re: interbase v postgresql |