Re: ERROR: XX001 (Critical and Urgent) - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: ERROR: XX001 (Critical and Urgent)
Date
Msg-id 4BE3E9BA0200002500031394@gw.wicourts.gov
Whole thread Raw
In response to Re: ERROR: XX001 (Critical and Urgent)  (Siddharth Shah <siddharth.shah@elitecore.com>)
Responses Re: ERROR: XX001 (Critical and Urgent)
List pgsql-admin
Siddharth Shah <siddharth.shah@elitecore.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

pgsql-admin by date:

Previous
From: Lacey Powers
Date:
Subject: Re: postgres invoked oom-killer
Next
From: Greg Spiegelberg
Date:
Subject: Re: postgres invoked oom-killer