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 1D4A5D1D5D9
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Tue,  9 Mar 2004 04:55:54 +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 14699-04
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Tue,  9 Mar 2004 00:55:51 -0400 (AST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by svr1.postgresql.org (Postfix) with ESMTP id B2114D1B53C
	for <pgsql-sql@postgresql.org>; Tue,  9 Mar 2004 00:55:50 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i294tnRa020429;
	Mon, 8 Mar 2004 23:55:50 -0500 (EST)
To: "David Witham" <davidw@unidial.com.au>
Cc: pgsql-sql@postgresql.org
Subject: Re: ANALYZE error 
In-reply-to: <CFA248776934FD43847E740E43C346D199DC67@ozimelb03.ozicom.com> 
References: <CFA248776934FD43847E740E43C346D199DC67@ozimelb03.ozicom.com>
Comments: In-reply-to "David Witham" <davidw@unidial.com.au>
	message dated "Tue, 09 Mar 2004 15:22:51 +1100"
Date: Mon, 08 Mar 2004 23:55:49 -0500
Message-ID: <20428.1078808149@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200403/68
X-Sequence-Number: 17167

"David Witham" <davidw@unidial.com.au> writes:
> Occasionally I get this error message from the analyze job:
> ERROR:  simple_heap_update: tuple concurrently updated
> What does this mean and should I do anything about it?

You can get this if two ANALYZEs run in parallel for the same table;
whichever one tries to update pg_statistic second fails with the above
error.  It's moderately annoying, but not dangerous.

			regards, tom lane