From: Matthew Nuzum <matthew.nuzum@canonical.com>
To: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performace Optimization for Dummies
Date: Thu, 28 Sep 2006 22:08:37 -0500
Message-ID: <451C8E35.7000906@canonical.com> (raw)
In-Reply-To: <efhdcr$2873$1@news.hub.org>
References: <efgu4v$276m$1@news.hub.org>
<b42b73150609281017m7f8f9d86xfa32d38cec954af7@mail.gmail.com>
<efh26m$2fd$1@news.hub.org>
<451C18BE.8050908@canonical.com>
<efhdcr$2873$1@news.hub.org>
Carlo Stonebanks wrote:
> Lots of great info here, I will see what applies to my situation. However, I
> don't see bulk inserts of the tables working, because all of the tables need
> to be refreshed as values to deduplicate and match will change with every
> row added. In order for this to work, i would have to write queries against
> the hash tables. This is where something like MySQL's in-memory tables would
> have come in handy...
>
> What is GDB?
>
> Carlo
Sorry, meant GDBM (disk based hash/lookup table).
With Postgres if your tables fit into RAM then they are in-memory as
long as they're actively being used.
Hashtables and GDBM, as far as I know, are only useful for key->value
lookups. However, for this they are *fast*. If you can figure out a way
to make them work I'll bet things speed up.
--
Matthew Nuzum
newz2000 on freenode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matthew.nuzum@canonical.com, stonec.register@sympatico.ca
Subject: Re: Performace Optimization for Dummies
In-Reply-To: <451C8E35.7000906@canonical.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox