Strange problem when upgrading to 7.2 with pg_upgrade.

I've started playing around with 7.2 on one of my development machines.
I decided to try the pg_upgrade program, something I usually never do.

Anyway, I followed the steps in the pg_upgrade (going from 7.1.3 to
7.2), and then when I started the database up after the upgrade finished
and vacuumed one of my tables, i get these error messages from the
postmaster. After this point I cannot restart the postmaster without
resetting the xlog.

I've kept the PGDATA directory around incase someone thinks this is
worth looking into, i would be more than happy to help out.

If i migrate the data over manually like a always do (pg_dump then
pg_restore), i don't have any problems. Part of the problem might be
path names for shared libraries specified in CREATE FUNCTION; I started
using pg back when it was version 6 before '$libdir' was supported and I
haven't bothered to take the absolute path names out yet -- i've just
updated it with each release (each release is installed in a different
location in case i need to roll back, and so i can test multiple version
at one time). not sure if pg_upgrade even checks for this.

oby/pgsql(at)loopy pg_upgrade]$ /moby/pgsql-7.2/bin/postmaster -i -o -F -B
256 -D/mo
DEBUG: database system was shut down at 2002-02-14 12:20:53 MST
DEBUG: checkpoint record is at 1/A7000010
DEBUG: redo record is at 1/A7000010; undo record is at 1/A7000010;
shutdown TRUE
DEBUG: next transaction id: 589031; next oid: 19512
DEBUG: database system is ready

DEBUG: --Relation developer--
DEBUG: Pages 669: Changed 0, Empty 0; Tup 51508: Vac 0, Keep 0, UnUsed
0.
Total CPU 0.07s/0.03u sec elapsed 0.11 sec.
DEBUG: Analyzing developer
FATAL 2: read of clog file 0, offset 139264 failed: Success
DEBUG: server process (pid 17786) exited with exit code 2
DEBUG: terminating any other active server processes
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
DEBUG: all server processes terminated; reinitializing shared memory
and semaphores
DEBUG: database system was interrupted at 2002-02-14 12:20:58 MST
DEBUG: checkpoint record is at 1/A7000010
DEBUG: redo record is at 1/A7000010; undo record is at 1/A7000010;
shutdown TRUE
DEBUG: next transaction id: 589031; next oid: 19512
DEBUG: database system was not properly shut down; automatic recovery
in progress
DEBUG: redo starts at 1/A7000050
FATAL 2: read of clog file 0, offset 139264 failed: Success
DEBUG: startup process (pid 17788) exited with exit code 2
DEBUG: aborting startup due to startup process failure
[postgres(at)loopy pg_upgrade]$
[postgres(at)loopy pg_upgrade]$
[postgres(at)loopy pg_upgrade]$
[postgres(at)loopy pg_upgrade]$ df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda8 248895 192496 43549 82% /
/dev/hda1 31079 4988 24487 17% /boot
/dev/hda5 24080660 6601476 17479184 28% /home
/dev/hda6 5044156 1930892 2857032 41% /usr
/dev/hda9 248895 133875 102170 57% /var
/dev/hdd1 59919196 39090008 20829188 66% /disk
oby/pgsql(at)loopy pg_upgrade]$ /moby/pgsql-7.2/bin/postmaster -i -o -F -B
256 -D/mo
DEBUG: database system was interrupted being in recovery at 2002-02-14
12:21:06 MST
This probably means that some data blocks are corrupted
and you will have to use the last backup for recovery.
DEBUG: checkpoint record is at 1/A7000010
DEBUG: redo record is at 1/A7000010; undo record is at 1/A7000010;
shutdown TRUE
DEBUG: next transaction id: 589031; next oid: 19512
DEBUG: database system was not properly shut down; automatic recovery
in progress
DEBUG: redo starts at 1/A7000050
FATAL 2: read of clog file 0, offset 139264 failed: Success
DEBUG: startup process (pid 17793) exited with exit code 2
DEBUG: aborting startup due to startup process failure
[postgres(at)loopy pg_upgrade]$