Re: more corruption

From: Tim Perdue <tperdue(at)valinux(dot)com>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: pgsql-hackers(at)hub(dot)org
Subject: Re: more corruption
Date: 2000-07-10 03:26:33
Message-ID: 39694269.A5D9025@valinux.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker wrote:
> just a quick thought ... have you tried shutting down and restrating the
> postmaster? basically, "reset" the shared memory? v7.x handles
> corruptions like that alot cleaner, but previous versions caused odd
> results if shared memory got corrupted ...

Well, I've rebooted twice. In fact, it was a hard lock that caused the
problems. When the machine was brought back up, the db was foobar.

I'm doing something really really evil to avoid losing the last days'
data:

-I created a new db
-used the old db schema to create all new blank tables
-copied the physical table files from the old data directory into the
new database directory
-currently vacuuming the new db - nothing is barfing yet
-now hopefully I can create my indexes and be back in business

Tim

--
Founder - PHPBuilder.com / Geocrawler.com
Lead Developer - SourceForge
VA Linux Systems
408-542-5723

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-07-10 03:36:12 Re: more corruption
Previous Message The Hermit Hacker 2000-07-10 03:13:13 Re: more corruption