Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 09161133740B for ; Tue, 19 Apr 2011 11:00:52 -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 73679-10 for ; Tue, 19 Apr 2011 14:00:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 555B31337BD7 for ; Tue, 19 Apr 2011 11:00:33 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Tue, 19 Apr 2011 09:00:33 -0500 Message-Id: <4DAD4F27020000250003C9E2@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Tue, 19 Apr 2011 09:00:23 -0500 From: "Kevin Grittner" To: "Selva manickaraja" , Subject: Re: Orphan Temp Table After PITR References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201104/174 X-Sequence-Number: 37355 Selva manickaraja wrote: > We encountered this for the 3rd time after completing a PITR. > 2011-04-19 12:12:59 MYT LOG: autovacuum: found orphan temp table > "pg_temp_108"."session_id" in database "np" > [for many different temp tables] > Anyone has any idea why this is happening? There were a lot of temp tables open on the master when you made the base backup? It would seem autovacuum is cleaning them up when it comes across them. Do you have some reason to believe that these "LOC" level entries represent some problem? -Kevin