Vacuum message

[Kevin Barnard]

I know I've seen this message before but I'm not quite sure what it
means. I think it's because I have two vacuums running over each
other. Does this sound right? It's comming from 7.4.x server.

ERROR: tuple concurrently updated

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Tom Lane]

Kevin Barnard <ke***********@gmail.com> writes:

I know I've seen this message before but I'm not quite sure what it
means. I think it's because I have two vacuums running over each
other. Does this sound right? It's comming from 7.4.x server. ERROR: tuple concurrently updated

Were they both VACUUM ANALYZEs? There's a known gotcha that if you
ANALYZE the same table concurrently in two different sessions, one
of them can fail this way when it goes to update the pg_statistic
entries. (Harmless, but annoying.) I don't know of any cause for
this message from a plain VACUUM though.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Kevin Barnard]

On Thu, 11 Nov 2004 13:56:48 -0500, Tom Lane <tg*@sss.pgh.pa.us> wrote:

Were they both VACUUM ANALYZEs? There's a known gotcha that if you
ANALYZE the same table concurrently in two different sessions, one
of them can fail this way when it goes to update the pg_statistic
entries. (Harmless, but annoying.) I don't know of any cause for
this message from a plain VACUUM though.

regards, tom lane

That's what it is I have cron jobs running over each other during heavy load.

Thanks

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)