Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 46D4E2E0303 for ; Wed, 13 Feb 2008 14:04:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 22586-08 for ; Wed, 13 Feb 2008 14:04:44 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 9460F2E02F7 for ; Wed, 13 Feb 2008 14:04:44 -0400 (AST) 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 m1DI4dON020170; Wed, 13 Feb 2008 13:04:39 -0500 (EST) To: Josh Berkus cc: pgsql-performance@postgresql.org Subject: Re: HOT TOAST? In-reply-to: <200802130950.15431.josh@agliodbs.com> References: <200802130950.15431.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Wed, 13 Feb 2008 09:50:15 -0800" Date: Wed, 13 Feb 2008 13:04:39 -0500 Message-ID: <20169.1202925879@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/146 X-Sequence-Number: 28688 Josh Berkus writes: > Does anyone know if HOT is compatible with pg_toast tables, or do TOASTed rows > simply get excluded from HOT? The current TOAST code never does any updates, only inserts/deletes. But the HOT logic should be able to reclaim deleted rows early via pruning. regards, tom lane