On Thu, 8 Dec 2005 11:59:24 -0500 , Amit V Shah [EMAIL PROTECTED]
wrote:
CONSTRAINT pk_runresult_has_catalogtable PRIMARY KEY
(runresult_id_runresult, catalogtable_id_catalogtable, value)
' - Index Scan using runresult_has_catalogtable_id_runresult
on runresult_has_catalogtable
On Dec 8, 2005, at 5:01 PM, Amit V Shah wrote:
Hi,
The thing is, although it shows 0.15 seconds, when I run the actual
query,
it takes around 40-45 seconds (sorry I forgot to mention that). And
then
sometimes it depends on data. Some parameters have very less number of
records, and
Hi all,
First of all, please pardon if the question is dumb! Is it even feasible or
normal to do such a thing ! This query is needed by a webpage so needs to be
lightning fast. Anything beyond 2-3 seconds is unacceptable performance.
I have two tables
CREATE TABLE runresult
(
id_runresult
@postgresql.org'
Subject: [PERFORM] Joining 2 tables with 300 million rows
Hi all,
First of all, please pardon if the question is dumb! Is it
even feasible or normal to do such a thing ! This query is
needed by a webpage so needs to be lightning fast. Anything
beyond 2-3 seconds is unacceptable
like that is even advisable at
all ...
Thanks,
Amit
-Original Message-
From: Dmitri Bichko [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 1:47 PM
To: Amit V Shah; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Joining 2 tables with 300 million rows
What's
