pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gourish Singbal <gourish@gmail.com>
To: Hemapriya <priyam_1121@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: data corruption
Date: Fri, 30 Sep 2005 11:36:41 +0530
Message-ID: <674d1f8a0509292306w51bca113o99e304cb10209cb1@mail.gmail.com> (raw)
In-Reply-To: <20050928191237.56381.qmail@web34212.mail.mud.yahoo.com>
References: <20050928191237.56381.qmail@web34212.mail.mud.yahoo.com>

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 indexes are been
used.
 regards
gourish singbal
 On 9/29/05, Hemapriya <priyam_1121@yahoo.com> 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=b.uid and a.origindb='04' and
> a.origindb=b.origindb and b.enteredon >='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

view thread (10+ messages)  latest in thread

Message-ID: <674d1f8a0509292306w51bca113o99e304cb10209cb1@mail.gmail.com>
Permalink:  ../674d1f8a0509292306w51bca113o99e304cb10209cb1@mail.gmail.com/
Also on:    postgresql.org/message-id/674d1f8a0509292306w51bca113o99e304cb10209cb1@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gourish@gmail.com, priyam_1121@yahoo.com
  Subject: Re: data corruption
  In-Reply-To: <674d1f8a0509292306w51bca113o99e304cb10209cb1@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox