Re: ERROR: XX001 (Critical and Urgent)

From: Siddharth Shah <siddharth(dot)shah(at)elitecore(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: ERROR: XX001 (Critical and Urgent)
Date: 2010-05-07 15:42:15
Message-ID: 4BE434D7.4050205@elitecore.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-novice

Kevin Grittner wrote:
> Siddharth Shah <siddharth(dot)shah(at)elitecore(dot)com> wrote:
>
>
>>>> xdb=# reindex index pg_class_relname_nsp_index;
>>>>
>>>> Now INDEXing taking High CPU and postgres baffled.
>>>>
>
>
>>> consider doing your recovery in single-user mode
>>>
>
>
>> postgres --single -P -D $DATADIR -p 5433 xdb
>> Same behavior in single mode.
>>
>
> How long did you leave it running? Did you get any messages? Is
> there anything in the log? What do CPU usage and disk usage look
> like during the attempt?
>
> -Kevin
>

Kevin, It start normally , I have successfully retrieved data from few
tables
But I am not able to do dS / dT or dt. As you said this is index file
for Postgres tables and indexes
Now when I taken call for reindex pg_class_relname_nsp_index it takes
99% CPU

PID PPID USER STAT VSZ %MEM %CPU COMMAND
13419 13418 nobody R 39172 8% 99% postgres --single -P -D
/var/db -p 5433 xdb
It's been running from 10 minutes still there is no output or logs.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Silvio Brandani 2010-05-07 15:42:38 Re: postgres invoked oom-killer
Previous Message Greg Spiegelberg 2010-05-07 15:35:54 Re: postgres invoked oom-killer

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2010-05-07 15:54:25 Re: ERROR: XX001 (Critical and Urgent)
Previous Message Kevin Grittner 2010-05-07 15:21:46 Re: ERROR: XX001 (Critical and Urgent)