Re: Power cut and performance problem - Mailing list pgsql-sql

From Daniel Caune
Subject Re: Power cut and performance problem
Date
Msg-id 1E293D3FF63A3740B10AD5AAD88535D201D30868@UBIMAIL1.ubisoft.org
Whole thread Raw
In response to Power cut and performance problem  ("Daniel Caune" <daniel.caune@ubisoft.com>)
Responses Re: Power cut and performance problem
List pgsql-sql
> BTW, I didn't complete my first thought above, which was to ask when
you
> last
> vacuumed the DB, but then I saw that you were running autovac, so that
> wasn't
> likely the problem.
>
> BTW, if the problem is actually a raid array that is rebuilding, it
should
> be
> (hopefullY) fixed by tomorrow morning.
>

An administrator is checking the raid status this morning.  Anyway, I
did some tests and it seems that some results are weird.

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?

--
Daniel


pgsql-sql by date:

Previous
From: Achilleus Mantzios
Date:
Subject: Re: Job queue, how would you implement this?
Next
From:
Date:
Subject: Referential integrity broken (8.0.3), sub-select help