optimizing Postgres queries

From: David Teran <david(dot)teran(at)cluster9(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: optimizing Postgres queries
Date: 2004-01-05 11:28:32
Message-ID: 4B0023AC-3F72-11D8-B3EB-000A95A6F0DC@cluster9.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Shridhar Daithankar 2004-01-05 11:35:55 Re: optimizing Postgres queries
Previous Message Tom Lane 2004-01-05 06:55:43 Re: Use my (date) index, darn it!