Re: Meaning of ERROR: tuple concurrently updated

From: KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at>
To:
Cc: Sql-Postgre <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Meaning of ERROR: tuple concurrently updated
Date: 2005-05-19 07:53:10
Message-ID: ED4E30DD9C43D5118DFB00508BBBA76EB16700@neptun.sonorys.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


|PFERL_Robert?= <robert(dot)koepferl(at)sonorys(dot)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
Tnaks.

No, I can't imagine any other instance that would issue a VACUUM ANALYZE at
the same time.
Could it be some kind of auto statistics which is updated all the time?

Would it be a solution to omit the ANALYZE and just do a VACUUM?
|

Browse pgsql-sql by date

  From Date Subject
Next Message KÖPFERL Robert 2005-05-19 09:11:48 Re: postgre variable
Previous Message Volkan YAZICI 2005-05-19 07:42:32 Re: postgre variable