Reply-To: <aalam@tatashare.com>
From: "Aftab Alam" <aalam@tatashare.com>
To: "'Jeff Frost'" <jeff@frostconsultingllc.com>,
	"'Daniel Caune'" <daniel.caune@ubisoft.com>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: Power cut and performance problem
Date: Wed, 22 Mar 2006 09:08:47 +0530
Message-ID: <003601c64d62$20db1400$ec1010ac@aftabn463>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.64.0603210747020.969@discord.dyndns.org>
Importance: Normal

unsubscribe

Regards,


-----Original Message-----
From: pgsql-sql-owner@postgresql.org
[mailto:pgsql-sql-owner@postgresql.org]On Behalf Of Jeff Frost
Sent: Tuesday, March 21, 2006 9:19 PM
To: Daniel Caune
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Power cut and performance problem


On Tue, 21 Mar 2006, Daniel Caune wrote:

> For example, the execution of the following query is fast as it used to
> be (gslog_event_id is the primary key on gslog_event):
>
>  select max(gslog_event_id) from gslog_event;  (=> Time: 0.773 ms)
>
>
> while the following query is really slow (several minutes):
>
>  select min(gslog_event_id) from gslog_event; (index on the primary key
> is taken)
>
>
> I'm not a hardware expert at all, but I supposed that the whole
> performance would be degraded when a problem occurs with RAID disks.  Am
> I wrong?  Could it be something else?  Are there some tools that check
> the state of a PostgreSQL database?

You would be correct, a hardware problem should manifest itself on both
those
queries.  What is the explain analyze output of those two queries?  It's
possible you have a corrupt index on gslog_event.  If that's the case, a
reindex would likely remedy the problem.  Is postgres logging any errors?

--
Jeff Frost, Owner 	<jeff@frostconsultingllc.com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly