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 79A17D1B9A4 for ; Wed, 21 Apr 2004 00:46:45 -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 58060-07 for ; Wed, 21 Apr 2004 00:46:44 -0300 (ADT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id 9280CD1B47D for ; Wed, 21 Apr 2004 00:46:43 -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 1BG8h1-000Ejw-7k; Tue, 20 Apr 2004 23:46:35 -0400 Message-ID: <4085EE81.9080309@zeut.net> Date: Tue, 20 Apr 2004 23:46:09 -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: Christopher Kings-Lynne Cc: Bruce Momjian , Jeff Boes , PostgreSQL-development Subject: Re: pg_autovacuum crashes when query fails for temp tables References: <200404201525.i3KFPp809934@candle.pha.pa.us> <4085D554.9010802@familyhealth.com.au> In-Reply-To: <4085D554.9010802@familyhealth.com.au> 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/604 X-Sequence-Number: 52526 Christopher Kings-Lynne wrote: > Does pg_autovacuum vacuum and analyze system catalog and TOAST tables > properly? Properly? I think so, that is to the best of my knowledge which is a bit limited :-) Toast Tables: pg_autovacuum doesn't do anything to toast tables explicitly. I am not aware that they need to be considered, I believe that if you vacuum table_foo which has an underlying toast table, then vacuum "does the right thing". Am I wrong? Someone please enlighten me if I am and I will fix. System Tables: pg_autovacuum treats non-shared system tables just like any other table. It monitors the activity and vacuums when it deems it appropriate. As for shared system tables: In user databases they are only analyzed by pg_autovacuum, while connected to template1, pg_autovacuum will treat the shared tables as normal tables and vacuum when appropriate. Does all this sound kosher? Thanks, Matthew