From: Iain <iain@mst.co.jp>
To: David Witham <davidw@unidial.com.au>
To: pgsql-sql@postgresql.org
Subject: Re: ANALYZE error
Date: Tue, 9 Mar 2004 14:15:35 +0900
Message-ID: <00c201c40595$8d822880$7201a8c0@mst1x5r347kymb> (raw)
References: <CFA248776934FD43847E740E43C346D199DC67@ozimelb03.ozicom.com>
>>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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: iain@mst.co.jp, davidw@unidial.com.au
Subject: Re: ANALYZE error
In-Reply-To: <00c201c40595$8d822880$7201a8c0@mst1x5r347kymb>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox