From: KÖPFERL Robert <robert.koepferl@sonorys.at>
Cc: Sql-Postgre <pgsql-sql@postgresql.org>
Subject: Meaning of ERROR: tuple concurrently updated
Date: Wed, 18 May 2005 17:50:18 +0200
Message-ID: <ED4E30DD9C43D5118DFB00508BBBA76EB166FF@neptun.sonorys.at> (raw)
Hi,
I have got some kind of FIFO-queue table.
New records are inserted and the oldest are DELETEd.
Thus I run VACUUM ANALYZE; every night by cron. However I keep getting
ERROR: tuple concurrently updated
My research lead me to the point that this is VACUUM tothether with the
INSERTs being issued to that table all the time.
But I didn't find a solution to avoid this. AFAIK now the table never gets
VACUUMed at all?
Please, what's really about that, how can it be avoided?
Thanks in advance
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: robert.koepferl@sonorys.at
Subject: Re: Meaning of ERROR: tuple concurrently updated
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB166FF@neptun.sonorys.at>
* 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