Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 094A62E004E for ; Fri, 28 Mar 2008 21:26:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 97746-04 for ; Fri, 28 Mar 2008 21:26:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3B0A32E0038 for ; Fri, 28 Mar 2008 21:26:54 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2T0QkpC017105; Fri, 28 Mar 2008 20:26:47 -0400 (EDT) To: Jeff Frost cc: pgsql-admin@postgresql.org Subject: Re: Strange issue with vacuum and temp tables In-reply-to: References: Comments: In-reply-to Jeff Frost message dated "Fri, 28 Mar 2008 17:09:42 -0700" Date: Fri, 28 Mar 2008 20:26:46 -0400 Message-ID: <17104.1206750406@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/245 X-Sequence-Number: 28728 Jeff Frost writes: > A look at the code revealed that the temp tables were created via normal > methods, so I'm curious to know if there is a bug regarding temp tables not > going away on Postgresql-8.2.x after the connection is closed? You aren't the first to report such a thing, but nobody has the foggiest idea how it could happen short of a backend crash. Have they had any crashes lately (or more specifically, around the mod times of those files, if you checked them)? Also, were the pg_temp schemas you zapped particularly high-numbered? Low-numbered ones would get cleaned out on the next use, but if the crash happened at a peak in the number of active backends it's easy to believe the files might hang around for awhile. regards, tom lane