pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chander Ganesan <chander@otg-nc.com>
To: e t <albunix@gmail.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: server crash, need to restore DB functionality
Date: Mon, 05 May 2008 18:18:49 -0400
Message-ID: <481F87C9.4070209@otg-nc.com> (raw)
In-Reply-To: <82d6a2d00804300515w7529cc67pb754d39ca6856f13@mail.gmail.com>
References: <82d6a2d00804291018h3f05bbe3gb21cae15eb7a0643@mail.gmail.com>
	<dcc563d10804291152l50ff2f01n1a3f29e59402f7cc@mail.gmail.com>
	<82d6a2d00804300515w7529cc67pb754d39ca6856f13@mail.gmail.com>

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!




view thread (6+ messages)

Message-ID: <481F87C9.4070209@otg-nc.com>
Permalink:  ../481F87C9.4070209@otg-nc.com/
Also on:    postgresql.org/message-id/481F87C9.4070209@otg-nc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: chander@otg-nc.com, albunix@gmail.com, scott.marlowe@gmail.com
  Subject: Re: server crash, need to restore DB functionality
  In-Reply-To: <481F87C9.4070209@otg-nc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox