X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 931E0D1EA3A for ; Tue, 20 Apr 2004 21:08:30 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 70839-09 for ; Tue, 20 Apr 2004 21:08:18 -0300 (ADT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id C207ED1F7B1 for ; Tue, 20 Apr 2004 19:33:51 -0300 (ADT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by www.postgresql.com (Postfix) with ESMTP id 06372CF67C6 for ; Tue, 20 Apr 2004 16:18:42 -0300 (ADT) Received: from ool-4352919e.dyn.optonline.net ([67.82.145.158] helo=matth.zeut.net) by outbound.mailhop.org with asmtp (Exim 4.20) id 1BG0lS-000OKN-Ay; Tue, 20 Apr 2004 15:18:38 -0400 Received: from 192.154.91.225 (SquirrelMail authenticated user dbmail2user); by matth.zeut.net with HTTP; Tue, 20 Apr 2004 14:19:09 -0400 (EDT) Message-ID: <37398.192.154.91.225.1082485149.squirrel@192.154.91.225> In-Reply-To: <40855DF0.3010300@idigx.com> References: <200404201525.i3KFPp809934@candle.pha.pa.us> <40855DF0.3010300@idigx.com> Date: Tue, 20 Apr 2004 14:19:09 -0400 (EDT) Subject: Re: pg_autovacuum crashes when query fails for temp From: "Matthew T. O'Connor" To: "Thomas Swan" Cc: "Bruce Momjian" , "Jeff Boes" , "PostgreSQL-development" , matthew@zeut.net User-Agent: SquirrelMail/1.5.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Mail-Handler: MailHop Outbound by DynDNS.org X-Report-Abuse-To: abuse@dyndns.org X-MHO-User: Zeut X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=PRIORITY_NO_NAME, RCVD_IN_NJABL, RCVD_IN_SORBS X-Spam-Level: * X-Archive-Number: 200404/589 X-Sequence-Number: 52511 > Bruce Momjian wrote: > Should pg_autovacuum be vacuuming temporary tables? This is a good question, and I would like some opinions from some other people more informed than I. > Secondly, why would > a temporary table for another session be visible to pg_autovacuum? I > know these may sound like stupid questions, but I'm a little shocked > that it found a temp table. Did someone make a permanent table, delete > it, and pg_autovacuum found it in between those operations? I will look into this when I have time, it certainly would be possible that pg_autovacuum could be tripped up by a sequence of events like you describe above. The more general problem is that it shouldn't crash even if it's vacuuming tables it shouldn't. Matthew