Ouch ... what version are you running, PG 7.0.2?
The best thing to do is to submit this problem to the postgres bugs mailing list. You'll have to register (it's a majordomo list). The core developers monitor this list and are responsive, even when people do things like try running PG 6.5's pg_dump on a PG 7.0.2 database :)
(you know who you are, and I'm still giggling over it!)
You can find the PG bug mailing list from the "info central" part of www.postgresql.org.
