"Florian G. Pflug" <fgp@xxxxxxxx> writes:
> So - does "tuple concurrently updated" make sense for "analyze"?
Yeah, it's entirely possible, if you have a background process that
might issue analyzes too (do you use autovacuum?). The error comes when
two sessions concurrently try to update the same row in pg_statistic.
I've looked at preventing it, but the cure seems worse than the disease
--- we don't really want ANALYZE to take any strong locks on the table,
and in any case all you are losing is presumably-near-duplicate stats
from one session or the other.
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
