In general, it seems to correspond to when there are a lot of inserts being run. I have one application that maybe does 10 inserts within 15 seconds or so, at which point the problem seems to crop up.
Any operation that does not use the qualified schema.entity names will error out (selects, inserts, updates) Taking your advice on upgrading both OS and pg version. I'll be back if that does not solve the issue ;-) Thanks for your time. -Rob -----Original Message----- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 10, 2004 2:30 PM To: Rob Klaus Cc: [EMAIL PROTECTED] Subject: Re: [GENERAL] Relation does not exist "Rob Klaus" <[EMAIL PROTECTED]> writes: > We are having a problem where intermittently a query will not work, > returning an error: > ERROR: Relation "x" does not exist > It will do this for a variable period, typically not lasting more than 5 > minutes This certainly seems like a bug, but I have no idea what's causing it. Can you characterize the conditions under which the bug appears or disappears? What operation exactly is getting the error, and what sorts of things are happening in parallel with it? > We are using PG_VERSION 7.3 on RedHat 7.0 Hm. Red Hat 7.0 is positively ancient; you really ought to update. And if you are running original PG 7.3 there are some very serious bugs that you ought to fix by updating to 7.3.6 (if not 7.4.something). But I can't say that I recognize your report as related to any of the known bug fixes. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
