From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | AlJeux <aljeux(at)free(dot)fr>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: vacuumdb: PANIC: corrupted item pointer |
Date: | 2007-07-10 23:46:41 |
Message-ID: | 12111.1184111201@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Huxton <dev(at)archonet(dot)com> writes:
>> First try was using a file system copy to reduce downtime as it was two
>> same 7.4.x version but the result was not working (maybe related to
>> architecture change 32bits => 64 bits) so I finally dropped the db and
>> performed an dump/restore. I think, the db was a mix of 32/64 bits files.
> Ah! That'll do it. You will get problems with a filesystem copy if
> 1. The database is running.
> 2. The architectures aren't identical
> 3. The installation options are different (a simple date option
> difference can cause problems)
PG 8.1 and later record MAXALIGN in pg_control.h, and will refuse to
start up if there is a 32/64 bit compatibility problem. But 7.4 has
no such defense. It does check for --enable-integer-datetimes
compatibility, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-07-11 00:04:41 | Re: exit code -1073741819 |
Previous Message | Tom Lane | 2007-07-10 23:34:08 | Re: Hyper-Trading |