| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: pg_class and relfilenode | 
| Date: | 2004-02-11 11:47:09 | 
| Message-ID: | 20040211114709.GB30118@phlogiston.dyndns.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Tue, Feb 10, 2004 at 08:29:50PM -0800, muteki muteki wrote:
> Hi,
> 
> I am currently having the corrupted tables issues
> described in the following link (possibly caused by
> power failure, which happens pretty often)
> http://archives.postgresql.org/pgsql-admin/2003-04/msg00012.php.
> Since we have our systems being deployed to numerous
> remote systems (psql 7.2.3), upgrading the entire database
> (with data migration) will be the least preferable
> solution.  I am thinking of creating a script that
You don't need to do any data migration to get off 7.2.3 -- 7.2.4 is
a drop-in replacement, so you should at least do that upgrade first.
But I don't think that power failures would be enough to cause the
kind of problem you're describing, unless you're running without
fsync or something.  Care to give more details?
In any case, I think that your script is mighty dangerous.  It sounds
like a recipe for data loss to me.  Postgres is considerably more
robust than this, and I think you're trying to cover up some serious
problems that you may have, likely with your hardware.
A
-- 
Andrew Sullivan  
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maneet Singh | 2004-02-11 12:03:18 | How to install Soundex() on Windows 2000 | 
| Previous Message | Andrew Sullivan | 2004-02-11 11:30:31 | Re: DB cache size strategies |