Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 76FDF37C687 for ; Mon, 12 Nov 2007 14:03:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 12105-10 for ; Mon, 12 Nov 2007 14:03:23 -0400 (AST) Received: from ro-out-1112.google.com (ro-out-1112.google.com [72.14.202.181]) by postgresql.org (Postfix) with ESMTP id 40A6F37C686 for ; Mon, 12 Nov 2007 14:03:29 -0400 (AST) Received: by ro-out-1112.google.com with SMTP id p4so1535773roc for ; Mon, 12 Nov 2007 10:03:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=gdQW+ppOLpScgUOKCY+Qbh+jQ9B8DkQlLMaSDNHw7KM=; b=GePG/QBEnjfTMg57XMtwRMSo7LGWOifSrOijmC7rDdO1hFQu2xvOE48WbfIeQt5LyCOmGPTFaxp55JQwIAvfNXDi7HQJ1xuxvJxgalo3ze+q5OUOOgiWEjbFG+1oo8FdaWXUPn3ed8ROoGhgR8slIv+AP57pAT9CWvIMrGHvNhQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=hdyMzz6O+0SgNDmr834zJzPCOWxvEbLerjUFlcdeqqr6LI0Hp8wGFYldGkTnrvKwlI5iqqoQUDww6hlcE2YXvBFsvpklBZeskfvxCX8qnG3mXvgh+U/quzD3dZMF+6oYtnfvuur7F+nRzQLz8twpzGEYN2YMdbsqAoPIjEvsr/o= Received: by 10.151.11.17 with SMTP id o17mr812703ybi.1194890604304; Mon, 12 Nov 2007 10:03:24 -0800 (PST) Received: from ?192.168.1.33? ( [82.12.225.47]) by mx.google.com with ESMTPS id 31sm487268nfu.2007.11.12.10.03.20 (version=SSLv3 cipher=RC4-MD5); Mon, 12 Nov 2007 10:03:23 -0800 (PST) Message-ID: <47389564.6010602@enterprisedb.com> Date: Mon, 12 Nov 2007 18:03:16 +0000 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.12 (X11/20070730) MIME-Version: 1.0 To: Scott Marlowe CC: Rafael Martinez , Tom Lane , pgsql-performance@postgresql.org Subject: Re: Need to run CLUSTER to keep performance References: <4732E6B4.1030907@usit.uio.no> <4732EF07.3060807@enterprisedb.com> <47332200.9050705@usit.uio.no> <24775.1194535980@sss.pgh.pa.us> <4738735B.6030408@usit.uio.no> <47387B4F.7000608@usit.uio.no> <473886DF.1050902@enterprisedb.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/187 X-Sequence-Number: 27602 Scott Marlowe wrote: > On Nov 12, 2007 11:01 AM, Heikki Linnakangas wrote: >> Scott Marlowe wrote: >>> So, between the first and second vacuum you had a long running >>> transaction that finally ended and let you clean up the dead rows. >> No, before 8.3, CLUSTER throws away non-removable dead tuples. So the >> long running transaction might still be there. > > Wow, good to know. Why would it have changed in 8.3? Was it > considered broken behaviour? I certainly considered it broken, though it was a known issue all along. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com