Tom,
Thanks again. Yes, I was able to create a dump file at that point so I
don't think it is a software bug. Besides, the view had been in use for
about a year and a half. We're going to run some memory and disk
diagnostics.
--Tim
Tom Lane wrote:
> tstump@regenstrief.org (Tim Stump) writes:
> > Thanks for the information. I manually deleted the view from the
> > pg_class table, but then I could not re-create the view (i.e., using
> > the same name). There must be some other system table that stores
> > information out there besides pg_class.
>
> pg_type would have an entry named for the view, too. Can't recall
> anything else that would give trouble.
>
> > At least I could create a
> > dump file of the entire database. Then I dropped the database and
> > restored from the dump file. After this, I was able to create the
> > view just fine.
>
> Can you dump it now? If there's actually a software bug here, I'd
> expect the same view definition to lead to the same complaint.
> But if you can dump it now, then I'd lean towards the
> corrupted-catalog-entry theory. Not that that should make you any
> happier ... have you run memory and disk diagnostics lately?
>
> regards, tom lane
