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 94472D1DA94 for ; Wed, 21 Apr 2004 00:51:35 -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 61738-04 for ; Wed, 21 Apr 2004 00:51:34 -0300 (ADT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id F31ACD1D52E for ; Wed, 21 Apr 2004 00:51:33 -0300 (ADT) Received: from ool-4353b51a.dyn.optonline.net ([67.83.181.26] helo=zeut.net) by outbound.mailhop.org with asmtp (Exim 4.20) id 1BG8ln-000HpX-7D; Tue, 20 Apr 2004 23:51:31 -0400 Message-ID: <4085EFC3.9020109@zeut.net> Date: Tue, 20 Apr 2004 23:51:31 -0400 From: "Matthew T. O'Connor" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Thomas Swan , Bruce Momjian , Jeff Boes , PostgreSQL-development Subject: Re: pg_autovacuum crashes when query fails for temp References: <200404201525.i3KFPp809934@candle.pha.pa.us> <40855DF0.3010300@idigx.com> <37398.192.154.91.225.1082485149.squirrel@192.154.91.225> <25435.1082518142@sss.pgh.pa.us> In-Reply-To: <25435.1082518142@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_NJABL, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200404/606 X-Sequence-Number: 52528 Tom Lane wrote: >"Matthew T. O'Connor" writes: > > >>This is a good question, and I would like some opinions from some other >>people more informed than I. >> >> > >You *can not* vacuum other sessions' temp tables; you don't have access >to the data. (You have no way to get at pages that are modified in >someone else's local buffer manager.) You could vacuum your own temp >tables, if you had any, but I would hardly expect autovacuum to have >any. > > Ok, so I will change pg_autovacuum to explicitly ignore temp tables. Just to be sure, I can do this by avoiding anything found in the pg_temp schemea, or is there a better way? Is it possible that a user could or would put a non-temp table the pg_temp schemea? >In reference to Chris' followup question, you *should* be vacuuming >system catalogs, and you *should not* be vacuuming TOAST tables. VACUUM >on a regular table automatically hits the associated TOAST table. > Ok, this is as I thought, pg_autovacuum is already doing the right thing here. (see the post I just sent a few minutes ago for more details). Thanks Tom, Matthew