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 94FEF53E18 for ; Mon, 9 May 2005 15:59:03 -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 72712-01 for ; Mon, 9 May 2005 18:58:57 +0000 (GMT) Received: from cmailm4.svr.pol.co.uk (cmailm4.svr.pol.co.uk [195.92.193.211]) by svr1.postgresql.org (Postfix) with ESMTP id 51CA553609 for ; Mon, 9 May 2005 15:58:54 -0300 (ADT) Received: from modem-2119.lemur.dialup.pol.co.uk ([217.135.136.71] helo=192.168.0.102) by cmailm4.svr.pol.co.uk with esmtp (Exim 4.41) id 1DVDSu-0000jp-1N; Mon, 09 May 2005 19:58:52 +0100 Subject: Re: conversion security update may have slowed our system? From: Simon Riggs To: Tom Lane Cc: =?iso-8859-2?Q?Sz=FBcs_G=E1bor?= , PGA In-Reply-To: <25256.1115646869@sss.pgh.pa.us> References: <427F5E01.1040404@gmail.com> <25256.1115646869@sss.pgh.pa.us> Content-Type: text/plain Organization: 2nd Quadrant Date: Mon, 09 May 2005 19:55:08 +0100 Message-Id: <1115664908.3830.33.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200505/94 X-Sequence-Number: 17523 On Mon, 2005-05-09 at 09:54 -0400, Tom Lane wrote: > =?ISO-8859-2?Q?Sz=FBcs_G=E1bor?= writes: > > 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? > > I can't see that there could be any connection. You need to be looking > for other explanations, not an "undo". Szucs, Your original release was 7.3.3 and you have just moved to 7.3.9. Thats a large jump to have made, so many things are likely to have changed. It doesn't seem likely that it was the 7.3.8 -> 7.3.9 jump, but many others things have changed. You need to establish some means of measuring your system's performance other than user reports, so you can verify problems objectively. Tom, It seems reasonable to publish some backout information with every patch to say whether or not it is possible to downgrade should a problem be found. That could also be accompanied with a "has not been tested" caveat if need be. Maybe Szucs hasn't found one this time, but there is a possibility and many people don't have a long time to decide with a production system looking unstable. Best Regards, Simon Riggs