Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id DECD765026C; Wed, 13 Aug 2008 21:53:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 10274-08; Wed, 13 Aug 2008 21:53:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 5775865024D; Wed, 13 Aug 2008 21:53:14 -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 m7E0rAlA018540; Wed, 13 Aug 2008 20:53:11 -0400 (EDT) To: Alvaro Herrera cc: pgsql-performance@postgresql.org, Pg Hackers Subject: Re: autovacuum: use case for indenpedent TOAST table autovac settings In-reply-to: <20080813212838.GA4683@alvh.no-ip.org> References: <20080813212838.GA4683@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Wed, 13 Aug 2008 17:28:38 -0400" Date: Wed, 13 Aug 2008 20:53:10 -0400 Message-ID: <18539.1218675190@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/161 X-Sequence-Number: 31042 Alvaro Herrera writes: > Does anyone see a need for having TOAST tables be individually > configurable for autovacuum? I've finally come around to looking at > being able to use ALTER TABLE for autovacuum settings, and I'm wondering > if we need to support that case. It seems like we'll want to do it somehow. Perhaps the cleanest way is to incorporate toast-table settings in the reloptions of the parent table. Otherwise dump/reload is gonna be a mess. regards, tom lane