Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 809C42E0038 for ; Mon, 5 May 2008 19:20:33 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 65112-03 for ; Mon, 5 May 2008 19:20:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from smtp162.iad.emailsrvr.com (smtp162.iad.emailsrvr.com [207.97.245.162]) by developer.postgresql.org (Postfix) with ESMTP id 217BC2E0032 for ; Mon, 5 May 2008 19:20:29 -0300 (ADT) Received: from relay6.relay.iad.emailsrvr.com (localhost [127.0.0.1]) by relay6.relay.iad.emailsrvr.com (SMTP Server) with ESMTP id B563B762751; Mon, 5 May 2008 18:20:28 -0400 (EDT) Received: by relay6.relay.iad.emailsrvr.com (Authenticated sender: chander-AT-otg-nc.com) with ESMTP id 88763762708; Mon, 5 May 2008 18:20:28 -0400 (EDT) Message-ID: <481F87C9.4070209@otg-nc.com> Date: Mon, 05 May 2008 18:18:49 -0400 From: Chander Ganesan User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: e t CC: Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: server crash, need to restore DB functionality References: <82d6a2d00804291018h3f05bbe3gb21cae15eb7a0643@mail.gmail.com> <82d6a2d00804300515w7529cc67pb754d39ca6856f13@mail.gmail.com> In-Reply-To: <82d6a2d00804300515w7529cc67pb754d39ca6856f13@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/32 X-Sequence-Number: 29116 e t wrote: > All, > > thanks for your kind reply. > > We are indeed running rhel 2 es, as our application requires such. > > I was able to correct this, including permission error, by > > 1)getting a right after the crash dump of the DB > 2)dropping the DB > 3)re-installing the RPM's via force option > 4)re-importing the DB > > I am not aware of how one re-indexes the table(s) If you imported from a dump, the indexes will be updated as part of the import. However, you would probably be well served to run a ANALYZE to update statistics information. Otherwise the query planner might come out with sub-optimal plans... I'm assuming that in the statement above you meant that you removed the cluster and restored the entire cluster. If you just did the DB, it's possible that other things might not be so well off....especially since you don't know the root cause of the problem. -- Chander Ganesan Open Technology Group, Inc. One Copley Parkway, Suite 210 Morrisville, NC 27560 919-463-0999/877-258-8987 http://www.otg-nc.com Ask me about expert on-site and public enrollment PostgreSQL training delivered worldwide!