X-Original-To: pgsql-sql-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 8974C9FB24B
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Tue, 29 Aug 2006 13:44:54 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 68085-04 for <pgsql-sql-postgresql.org@postgresql.org>;
	Tue, 29 Aug 2006 13:44:31 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from nf-out-0910.google.com (nf-out-0910.google.com
 [64.233.182.187])
	by postgresql.org (Postfix) with ESMTP id 33F559FB284
	for <pgsql-sql@postgresql.org>; Tue, 29 Aug 2006 13:44:29 -0300 (ADT)
Received: by nf-out-0910.google.com with SMTP id m18so135143nfc
	for <pgsql-sql@postgresql.org>; Tue, 29 Aug 2006 09:44:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=Z2mCACbjwPcF7zLVi21ZVsC1YMiaOOfLhBqnrHTyaRtRVwNgQeaH25w11tWGMJu7mDmqogZHehNmMuguw2Avs7fkg/POZEO1lW9FRZ2h8g38mIJpJMApwvl1hXoFfOpifaLGFDsVACLYxO1ONIV/Yy+yjKEYTixC4xq0aFbfS1Y=
Received: by 10.66.216.6 with SMTP id o6mr4666788ugg;
	Tue, 29 Aug 2006 09:44:28 -0700 (PDT)
Received: by 10.66.248.13 with HTTP; Tue, 29 Aug 2006 09:44:28 -0700 (PDT)
Message-ID: <7539aebb0608290944r40556b5fl2b047e845e68bd6c@mail.gmail.com>
Date: Tue, 29 Aug 2006 12:44:28 -0400
From: Sumeet <asumeet@gmail.com>
To: pgsql-sql@postgresql.org
Subject: 
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_18416_29678287.1156869868059"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=1.63 tagged_above=0 required=5 tests=AWL,
	DNS_FROM_RFC_ABUSE, HTML_00_10, HTML_MESSAGE, MISSING_SUBJECT, SPF_PASS
X-Spam-Level: *
X-Archive-Number: 200608/231
X-Sequence-Number: 26189

------=_Part_18416_29678287.1156869868059
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,

I'm having very strange problems with indexing, I have a large number of
partial indexes, when i try to run some queries sometimes the queries run
very fast and sometimes they are 100times slower than what i ran
before.....I tried running vacuum analyze couple of times and it dint help
me at all. Also i tried the explain analyze and what i found was the query
execution plan keeps on changes. Is there any better way to gain control
over these, I tried turning seqscan off, and messing with some other
parameters but dint really help. Also can somebody point me out to links
which explains more about query execution plans..i.e. each of parameters
like bitmap heap scan, index scan....etc...

-- 
Thanks,
Sumeet

------=_Part_18416_29678287.1156869868059
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,<br><br>I'm having very strange problems with indexing, I have a large number of partial indexes, when i try to run some queries sometimes the queries run very fast and sometimes they are 100times slower than what i ran before.....I tried running vacuum analyze couple of times and it dint help me at all. Also i tried the explain analyze and what i found was the query execution plan keeps on changes. Is there any better way to gain control over these, I tried turning seqscan off, and messing with some other parameters but dint really help. Also can somebody point me out to links which explains more about query execution plans..i.e. each of parameters like bitmap heap scan, index scan....etc...
<br><br>-- <br>Thanks,<br>Sumeet

------=_Part_18416_29678287.1156869868059--