> * Is it really a good idea for database-wide ANALYZE to run as a single > transaction? Holding all those locks is a recipe for deadlocks, even > if they're as inoffensive as AccessShareLocks normally are.
Wasn't one idea behind that change also to not make the planner create a plan from mixed old and new statistics ? I guess that could later be accomplished with "begin work; analyze; commit work;" (with subtransactions) though. Andreas ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
