Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> Actually the hack checks for oids, and doesn't make the index, if there
> isn't an oid in the table, so I tried it with a table without oids, and
> it still occurs.
My thought was that at this point the indexes on pg_attribute are very
possibly corrupt, and so just removing whatever initially caused that
corruption won't necessarily cause the error messages to stop. You
should reindex pg_attribute to get back into a good state.
regards, tom lane