From: David Teran <david.teran@cluster9.com>
To: pgsql-performance@postgresql.org
Subject: optimizing Postgres queries
Date: Mon, 5 Jan 2004 12:28:32 +0100
Message-ID: <4B0023AC-3F72-11D8-B3EB-000A95A6F0DC@cluster9.com> (raw)
Hi,
we are new to Postgres and we are evaluating Postgres 7.4 on MacOS X as
an alternative to FrontBase 3.6.27.
From the available features Postgres is the choice #1.
We have some tests to check the performance and FrontBase is about 10
times faster than Postgres. We already played around with explain
analyse select. It seems that for large tables Postgres does not use an
index. We often see the scan message in the query plan. Were can we
find more hints about tuning the performance? The database is about 350
MB large, without BLOB's. We tried to define every important index for
the selects but it seems that something still goes wrong: FrontBase
needs about 23 seconds for about 4300 selects and Postgres needs 4
minutes, 34 seconds.
Any clues?
regards David
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: david.teran@cluster9.com
Subject: Re: optimizing Postgres queries
In-Reply-To: <4B0023AC-3F72-11D8-B3EB-000A95A6F0DC@cluster9.com>
References: <4B0023AC-3F72-11D8-B3EB-000A95A6F0DC@cluster9.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