Re: Strange problem when upgrading to 7.2 with pg_upgrade.

[root(at)loopy pg_clog]# pwd
/moby/pgsql-upgrade-bad/pg_clog
[root(at)loopy pg_clog]# ls -la
total 9
drwx------ 2 postgres postgres 72 Feb 14 09:32 .
drwx------ 6 postgres postgres 304 Feb 14 16:02 ..
-rw------- 1 postgres postgres 8192 Feb 14 09:34 0000
[root(at)loopy pg_clog]# bzip2 < 0000 | uuencode -
begin 644 -
M0EIH.3%!62936<[:PW<``#Y_".;,1H``L!``9(at)!F``(`"```"#``V*#5/R*>
MHT--`TT!31H`T``"1"(TT*:#U/4>C]8_(/$);W"6=D0`'3$(Z9Y_D(V(at)K9T)
M+,\6"GDBTU?,C9R[NSB.6-X6M3\55RS<AS$:?0<,;N4/K>#.KV(E,[88LWG%
M[:QR6B"\'JK2G9LB*63"00449P7!2)#0O3IY4PT;P%DC'J$M$T3$5'RU5';2
A*:2EB*:1)!MI,SQ%1=GE_(FY2U#027L7<D4X4)#.VL-W
`
end
[root(at)loopy pg_clog]#

On Thu, 2002-02-14 at 17:54, Tom Lane wrote:
> Brian Hirt <bhirt(at)mobygames(dot)com> writes:
> > I decided to try the pg_upgrade program, something I usually never do.
>
> > FATAL 2: read of clog file 0, offset 139264 failed: Success
>
> Could we see ls -l $PGDATA/pg_clog?
>
> I suspect that pg_upgrade has neglected to make sure the clog is long
> enough.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)