Ok, that seems to have fixed it, so my next question is how did it get
corrupt?
Dave
On Tue, 2004-01-13 at 23:07, Tom Lane wrote:
> Dave Cramer <pg@fastcrypt.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
>
--
Dave Cramer
519 939 0336
ICQ # 1467551
