Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 5613E1337BA0
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 14 Mar 2011 04:55:13 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 45458-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 14 Mar 2011 07:55:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from rs73.luxsci.com (rs73.luxsci.com [64.49.254.135])
	by mail.postgresql.org (Postfix) with ESMTP id DEFD61337BCC
	for <pgsql-admin@postgresql.org>; Mon, 14 Mar 2011 04:55:04 -0300 (ADT)
Received: from GNANAM ([180.151.61.10]) (authenticated bits=0)
	by rs73.luxsci.com (8.13.8/8.13.8) with ESMTP id p2E7sxFc021958;
	Mon, 14 Mar 2011 02:55:01 -0500
Reply-To: <gnanam@zoniac.com>
From: "Gnanakumar" <gnanam@zoniac.com>
To: "'Rosser Schwarz'" <rosser.schwarz@gmail.com>
Cc: <pgsql-admin@postgresql.org>
References: <006d01cbdfd5$f48becb0$dda3c610$@com>
	<4D79FF3D020000250003B7C6@gw.wicourts.gov>
	<004f01cbe20c$f2c6a260$d853e720$@com>
	<AANLkTikOgLeit=eTEtin-+XX8Rb9rKbwahuUy62q3TBf@mail.gmail.com>
In-Reply-To: <AANLkTikOgLeit=eTEtin-+XX8Rb9rKbwahuUy62q3TBf@mail.gmail.com>
Subject: Re: PSQLException: ERROR: could not open relation with OID xxxx
Date: Mon, 14 Mar 2011 13:20:48 +0530
Organization: Zoniac Software Private Limited
Message-ID: <006201cbe21c$8a657e20$9f307a60$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcviFM0xM9vTftwuSyO0aI4xWuyKQAABh5mQ
Content-Language: en-us
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9
X-Spam-Level: 
X-Archive-Number: 201103/154
X-Sequence-Number: 37026

> Although it's unrelated to your query about an exception being raised,
> a word of advice on temporary tables.  (This may not be relevant to
> your situation, but it's no small source of pain in one of the systems
> I'm responsible for.)  Significant use of temporary tables will cause
> commensurately significant bloat in your system catalogs.  We have a
> system which, in the course of its "normal" operations, creates
> hundreds of temporary tables for processing, aggregation, analysis,
> and reporting.

Thank you very much for sharing your real-time experience.

Do you think that this "significantly bloated system catalogs" is caused
because of the old version 8.2.3 we're running?  Will this be resolved in
latest PostgreSQL v9.0?  BTW, what version of PostgreSQL are you handling?

Doc says: " Temporary tables are automatically dropped at the end of a
session, or optionally at the end of the current transaction (see ON COMMIT
below). Any indexes created on a temporary table are automatically temporary
as well."
If temporary tables and its indexes are automatically dropped at the end of
the session, why would it cause bloat in system catalogs?  I hope you can
make me understand by sharing your real-time experience.

Again, thanks for your advice.