X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E05FFD1B53C for ; Tue, 9 Mar 2004 05:15:57 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 18590-08 for ; Tue, 9 Mar 2004 01:15:55 -0400 (AST) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 0A4ECD1B905 for ; Tue, 9 Mar 2004 01:15:53 -0400 (AST) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id i295Fbv21733; Tue, 9 Mar 2004 14:15:37 +0900 Message-ID: <00c201c40595$8d822880$7201a8c0@mst1x5r347kymb> From: "Iain" To: "David Witham" , References: Subject: Re: ANALYZE error Date: Tue, 9 Mar 2004 14:15:35 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/69 X-Sequence-Number: 17168 >>The only other job that could be running is a vacuum I run at 1am but I don't think it would take an hour to run. Famous last words... :-) It should be easy to check this, but I don't know if that is a likely source of problems anyway. If I were you I'd just do VACUUM ANALYSE in one comand. It would certainly eliminate that as a factor. At this stage you have no idea which table it occurs on, or if it always happens on the same table, or at the same time, am I right? Failing any more useful response from those with more internal knowledge you may have to resort to collecting information and trying to isolate the problem. It would be a good idea to give all the relevant version numbers too regards iain