Message-ID: <4E1E2F80.30709@pinpointresearch.com>
Date: Wed, 13 Jul 2011 16:51:28 -0700
From: Steve Crawford <scrawford@pinpointresearch.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: "pgsql-admin@postgresql.org Admin" <pgsql-admin@postgresql.org>
Subject: Re: could not open relation with OID
References: <4E1E1CFE.2030500@pinpointresearch.com>
	<12791.1310599941@sss.pgh.pa.us>
In-Reply-To: <12791.1310599941@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/13/2011 04:32 PM, Tom Lane wrote:
> Steve Crawford<scrawford@pinpointresearch.com>  writes:
>> I've seen the "could not open relation with OID" error a couple times
>> recently ...
> Not worry....
> You might be able to dodge the problem by excluding temp relations from
> the reporting query, though whether the sum of only non-temp rel sizes
> is of value to you is hard to guess from here.
Data safety was my concern. The error is so rare that I can ignore it. 
(The two I saw are the first in the 2+ years this server has been active 
and were probably the result of running the report manually when the 
database was active rather than the usual nighttime cron-run).

Cheers,
Steve