From: | "Tony Carter" <tony(at)iat(dot)net> |
---|---|
To: | "Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: large database on postgres |
Date: | 2002-06-14 22:31:40 |
Message-ID: | DJEGLLPNDIAAIGPJHAALCEEBDFAA.tony@iat.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Stephan,
Here is more info. I don't have access to the server right now, I'll do the
explain analyze later.
table:stock_history
name type
------------------------------
id int not null pk
name varchar 250 not null index
sql statement:
select id from stock_history where name = "quest";
takes about 2 minutes.
TIA,
Tony
-----Original Message-----
From: Stephan Szabo [mailto:sszabo(at)megazone23(dot)bigpanda(dot)com]
Sent: Friday, June 14, 2002 5:17 PM
To: Tony Carter
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] large database on postgres
On Thu, 13 Jun 2002, Tony Carter wrote:
> Hello,
> I have one application that I'm trying to move the db to pgsql. The db
> contains around 15 million rows of data. I'm running into 10 second delays
> when doing a simple select on an index column.
>
> My test box is Linux 1ghz Celeron 25MB Ram, 7200rpm IDE drive. I know I
> need SCSI but is there any tuning I can do to speed this up?
Well, let's do the standard info requests :)
Have you used vacuum analyze? What's the schema, query, and explain (or
explain analyze if you're using 7.2) output for the query.
From | Date | Subject | |
---|---|---|---|
Next Message | chris.gamble | 2002-06-14 23:32:29 | Problem with an SQL function |
Previous Message | Tom Lane | 2002-06-14 22:25:53 | Re: I must be blind... |