X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9628D53653 for ; Mon, 9 May 2005 09:57:10 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12646-08 for ; Mon, 9 May 2005 12:57:07 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by svr1.postgresql.org (Postfix) with ESMTP id B6AC353623 for ; Mon, 9 May 2005 09:57:06 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so2033580wra for ; Mon, 09 May 2005 05:57:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding; b=ZvAiLymktMCI+io+Xtt8YJwqUC46M+zuN/i8KrBmZMFIyPA5DaDYZEHvV7qhL4BcYpjpKwQGnwwXYYM8c0Ues8D06kCwM8YZBgfDAp93bv+GvVrelGHenfyZByF//DxnlJ4mlazx59tL4Ar3XHiCdRwfyWisDNOStnhZePMrhH4= Received: by 10.54.6.32 with SMTP id 32mr2546192wrf; Mon, 09 May 2005 05:57:11 -0700 (PDT) Received: from ?192.168.3.4? ([81.182.248.121]) by mx.gmail.com with ESMTP id 35sm1079411wra.2005.05.09.05.57.10; Mon, 09 May 2005 05:57:11 -0700 (PDT) Message-ID: <427F5E01.1040404@gmail.com> Date: Mon, 09 May 2005 14:56:33 +0200 From: =?ISO-8859-2?Q?Sz=FBcs_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: PGA Subject: conversion security update may have slowed our system? Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.388 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200505/89 X-Sequence-Number: 17518 Dear Gurus, I dunno if it should go to -perform or -bugs, so stay with the original message. As Tom wrote in http://archives.postgresql.org/pgsql-announce/2005-05/msg00001.php as well as at http://www.postgresql.org/about/news.315, I patched all our testing (7.4.6) and production databases (7.3.3) on Thursday. According to user reports, the production server slowed down noticeably on Friday and is almost unbearably slow today (Monday). My humble question is, could you think of any way this patch could affect overall speed, or is it just a fatal coincidence? System: Debian "Woody" @ DualXeon 2.4 1G 5x10krpm scsi hw raid 5 IBM server Kernel 2.4.30 (patched on Tuesday, 3 days before first syndroms TESTS: 1. As far as we could test without modifying the prod.db (i.e. issuing updates/inserts), this server makes both simple (select *) and joined queries in about twice the time of an Athlon 2k server on 7.4. VACUUM FULL VERBOSE ANALYZE and ANALYZE in itself did not help. 2. Set up another database, to see if it's in-db issue, but it made no difference. 3. Set up another database, based on a pre-patch dump (but I think it's irrelevant since I also patched template0, but it made no difference. Any ideas? Since I haven't checked it before, could you please provide an "undo" for a 7.3.3 database? (I assume it's a similar update, but don't know the original ACL values) Yours, -- G.