From: | "Marc Mitchell" <marcm(at)eisolution(dot)com> |
---|---|
To: | "Derek Hamilton" <derek(at)capweb(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Performance Expectations |
Date: | 2003-04-18 18:48:46 |
Message-ID: | 006c01c305db$28050460$6701050a@eisolution.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I would suggest simply doing an EXPLAIN on your query and examining the
output. It will tell you whether your index is being used or not. That's
a big first step in determining what your optimal performance expectations
should be.
Marc Mitchell - Senior Application Architect
Enterprise Information Solutions, Inc.
4910 Main Street
Downers Grove, IL 60515
(630) 512-0570
marcm(at)eisolution(dot)com
----- Original Message -----
From: "Derek Hamilton" <derek(at)capweb(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Sent: Friday, April 18, 2003 1:24 PM
Subject: [ADMIN] Performance Expectations
> Hello all,
>
> We're using PostgresQL with a fairly large database (about 2GB). I have
one
> table that currently exceeds 4.5 million records and will probably grow
to
> well over 5 fairly soon. The searching of this table is basically done
on
> one field, which field I have set up a btree index on. My question is,
if I
> search this table and get the results back in about 6-7 seconds is that
> pretty good, not so good...? What are the things I should look at in
> determining the performance on this?
>
> BTW, forgive the lack of information. I'd be happy to post more info on
the
> table, hardware, etc. I just didn't want to overwhelm the initial
question.
>
> Thanks,
> Derek Hamilton
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Biagioni | 2003-04-18 18:56:02 | Re: <no subject> |
Previous Message | Andrew Biagioni | 2003-04-18 18:33:23 | Re: deadlock detection |