On Thu, 11 Nov 2004 13:56:48 -0500, Tom Lane <[EMAIL PROTECTED]> 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. (Harm
Kevin Barnard <[EMAIL PROTECTED]> 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
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)---
