X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 588E9D8171 for ; Fri, 30 Sep 2005 03:06:48 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19848-03 for ; Fri, 30 Sep 2005 06:06:43 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by svr1.postgresql.org (Postfix) with ESMTP id 5ECA2D8068 for ; Fri, 30 Sep 2005 03:06:40 -0300 (ADT) Received: by zproxy.gmail.com with SMTP id z31so340911nzd for ; Thu, 29 Sep 2005 23:06:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pMsZObjwRFJDQvil5JIVejc7RrATl8i+RKKih44n5WOC+S/U9KxuOhyV2nnZ3LfKA4GldP3zf2Tr3fDEL/FcOMvBZYx0CtCMvXWBECrq6acLiqJJhBiSnGkaKr6hjEhHm/5iMc6IdgfdnvMM/7EmKaNAGAIu+VrR52HVxR26ajs= Received: by 10.36.75.12 with SMTP id x12mr5287795nza; Thu, 29 Sep 2005 23:06:41 -0700 (PDT) Received: by 10.36.74.7 with HTTP; Thu, 29 Sep 2005 23:06:41 -0700 (PDT) Message-ID: <674d1f8a0509292306w51bca113o99e304cb10209cb1@mail.gmail.com> Date: Fri, 30 Sep 2005 11:36:41 +0530 From: Gourish Singbal Reply-To: Gourish Singbal To: Hemapriya Subject: Re: data corruption Cc: pgsql-admin@postgresql.org In-Reply-To: <20050928191237.56381.qmail@web34212.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_696_27673892.1128060401400" References: <20050928191237.56381.qmail@web34212.mail.mud.yahoo.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.107 required=5 tests=[AWL=0.026, HTML_30_40=0.056, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200509/329 X-Sequence-Number: 19066 ------=_Part_696_27673892.1128060401400 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline priya, I would suggest do a vacuum full analyze verbose on both the tables. and than explain analyze command to check if proper indexes are bee= n used. regards gourish singbal On 9/29/05, Hemapriya wrote: > > Hi, > > I have a query that runs fine for one set of data and > not for another. > > In the following query, all the columns used in a > where > clause are indexed. If i use this for the > origindbs('02','05','06','07') except '04', it works > fine. > when i look for the data from origindb "04" it just > run for 2 hours. > > "select count(*) from qpassextrequest a,request b > where a.requestFK=3Db.uid and a.origindb=3D'04' and > a.origindb=3Db.origindb and b.enteredon >=3D'2005-09-28' > and b.enteredon < '2005-09-29'" > > What could be the reason.. Can that be a index or data > corruption? If so, rebuiding the index will solve the > problem? > > Any hint is appreciated. > > Thanks > Priya > > > > > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- Best, Gourish Singbal ------=_Part_696_27673892.1128060401400 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
 
priya,
 
I would suggest do a vacuum full analyze verbose <tablename> on = both the tables.
and than explain analyze <query> command to check if proper inde= xes are been used.
 
regards
gourish singbal
 
On 9/29/05, = Hemapriya <priyam_1121@yaho= o.com> wrote:
Hi,

I have a query that r= uns fine for one set of data and
not for another.

In the followin= g query, all the columns used in a
where
clause are indexed. If i use this for the
origindbs('02','0= 5','06','07') except '04', it works
fine.
when i look for the data fr= om origindb "04" it just
run for 2 hours.

"select = count(*) from qpassextrequest a,request b
where a.requestFK=3Db.uid and a.origindb=3D'04' and
a.origindb=3Db.o= rigindb and b.enteredon >=3D'2005-09-28'
and b.enteredon < '2005-0= 9-29'"

What could be the reason.. Can that be a index or datacorruption? If so, rebuiding the index will solve the
problem?

Any hint is appreciated.

Thanks
Priya

=



__________________________________
Yahoo! Mail - PC Maga= zine Editors' Choice 2005
http://mail.= yahoo.com

---------------------------(end of broadcast)------------------= ---------
TIP 4: Have you searched our list archives?

  = ;            http://archives.postgresql.org



--
Best,
Gouris= h Singbal=20 ------=_Part_696_27673892.1128060401400--