Thread: Meaning of ERROR: tuple concurrently updated

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

KÖPFERL 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