From: Tom Lane <tgl@sss.pgh.pa.us>
To: KÖPFERL Robert <robert.koepferl@sonorys.at>
Cc: Sql-Postgre <pgsql-sql@postgresql.org>
Subject: Re: Meaning of ERROR: tuple concurrently updated
Date: Wed, 18 May 2005 12:00:03 -0400
Message-ID: <22416.1116432003@sss.pgh.pa.us> (raw)
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB166FF@neptun.sonorys.at>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB166FF@neptun.sonorys.at>
=?ISO-8859-1?Q?K=D6PFERL_Robert?= <robert.koepferl@sonorys.at> writes:
> Thus I run VACUUM ANALYZE; every night by cron. However I keep getting
> ERROR: tuple concurrently updated
Have you got other processes also doing VACUUM ANALYZE? The only known
reason for this to happen is that two processes concurrently ANALYZE the
same table and conflict when they both try to update the same
pg_statistic rows.
regards, tom lane
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: tgl@sss.pgh.pa.us, robert.koepferl@sonorys.at
Subject: Re: Meaning of ERROR: tuple concurrently updated
In-Reply-To: <22416.1116432003@sss.pgh.pa.us>
* 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