Re: pg_inherits: not found, but visible [IT GETS WORSE] - Mailing list pgsql-hackers

From Joel Burton
Subject Re: pg_inherits: not found, but visible [IT GETS WORSE]
Date
Msg-id Pine.LNX.4.21.0103201957440.20139-100000@olympus.scw.org
Whole thread Raw
In response to Re: pg_inherits: not found, but visible  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_inherits: not found, but visible [IT GETS WORSE]  ("Ross J. Reedstrom" <reedstrm@rice.edu>)
Re: pg_inherits: not found, but visible [IT GETS WORSE]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Yikes. It gets weirder.

Fixed the pg_inherits problem, went back to my Zoping, trying to optimize
some views, and during another run, get an error that trelclasspq, one of
my tables, couldn't open.

Trying this out in psql, I get the same error message--the file doesn't
exist. And, getting the oid for the file, looked in the directory--and
this file is gone too!

Now, I just made a good dump of the database, so I can always go  back to
that. But this seems to be a *serious* problem in the system.

I have

Zope 2.3.1b2 (most recent version of Zope)
running on a Linux-Mandrake 7.2 box (server #1)

It has a database adapter called ZPoPy, which is the Zope version of PoPy,
a Python database adapter for PostgreSQL.

PoPy is getting data from my PostgreSQL database, which is 7.1beta4, and
served on a different Mandrake 7.2 box.

Has anyone seen anything like this?

I doubt the error is Zope *per se*, since Zope can only talk to the
database adapter, and I doubt the database adapter has the intentional
feature of delete-the-file-for-this-table in its protocol. It *could* be a
problem w/ZPoPy or PoPy; I'll send a message to their list as well.

Thanks!

-- 
Joel Burton   <jburton@scw.org>
Director of Information Systems, Support Center of Washington



pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Final Call: RC1 about to go out the door ...
Next
From: Tom Lane
Date:
Subject: Re: Beta 6 Regression results on Redat 7.0.