From: Gnanakumar <gnanam@zoniac.com>
To: 'Kevin Grittner' <Kevin.Grittner@wicourts.gov>
To: pgsql-admin@postgresql.org
Subject: Re: PSQLException: ERROR: could not open relation with OID xxxx
Date: Tue, 15 Mar 2011 12:38:07 +0530
Message-ID: <003601cbe2df$bf0c7480$3d255d80$@com> (raw)
In-Reply-To: <4D7DEB6B020000250003B821@gw.wicourts.gov>
References: <006d01cbdfd5$f48becb0$dda3c610$@com>
<4D7DEB6B020000250003B821@gw.wicourts.gov>
> Clearly it's trying to use an OID it calculated for one of these
> tables after the table has been dropped, and I suspect that the lock
> is released between gathering the data and sorting it. I don't have
> any 8.2 databases around to try this on, but perhaps you would avoid
> it with a slight rearrangement of your monitoring query:
Thanks for both making this clear and providing an rearranged/modified
version of my original query. I'll try out this option also.
> If that doesn't do it I might try adding zero to numbers and
> concatenating empty strings to try to prevent late use of the OID.
> (Essentially as a form of optimization barrier.)
I couldn't understand this approach clearly. Can you help explain me with
some example?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gnanam@zoniac.com, Kevin.Grittner@wicourts.gov
Subject: Re: PSQLException: ERROR: could not open relation with OID xxxx
In-Reply-To: <003601cbe2df$bf0c7480$3d255d80$@com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox