pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedMeaning of ERROR: tuple concurrently updated
3+ messages / 2 participants
[nested] [flat]
* Meaning of ERROR: tuple concurrently updated
@ 2005-05-18 15:50 KÖPFERL Robert <robert.koepferl@sonorys.at>
2005-05-18 16:00 ` Re: Meaning of ERROR: tuple concurrently updated Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: KÖPFERL Robert @ 2005-05-18 15:50 UTC (permalink / raw)
To: ; +Cc: pgsql-sql
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Meaning of ERROR: tuple concurrently updated
2005-05-18 15:50 Meaning of ERROR: tuple concurrently updated KÖPFERL Robert <robert.koepferl@sonorys.at>
@ 2005-05-18 16:00 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Tom Lane @ 2005-05-18 16:00 UTC (permalink / raw)
To: KÖPFERL Robert <robert.koepferl@sonorys.at>; +Cc: pgsql-sql
=?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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Meaning of ERROR: tuple concurrently updated
@ 2005-05-19 07:53 KÖPFERL Robert <robert.koepferl@sonorys.at>
0 siblings, 0 replies; 3+ messages in thread
From: KÖPFERL Robert @ 2005-05-19 07:53 UTC (permalink / raw)
To: ; +Cc: pgsql-sql
|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
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?
|
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2005-05-19 07:53 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-05-18 15:50 Meaning of ERROR: tuple concurrently updated KÖPFERL Robert <robert.koepferl@sonorys.at>
2005-05-18 16:00 ` Re: Meaning of ERROR: tuple concurrently updated Tom Lane <tgl@sss.pgh.pa.us>
2005-05-19 07:53 Re: Meaning of ERROR: tuple concurrently updated KÖPFERL Robert <robert.koepferl@sonorys.at>
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