Bruce Momjian <[EMAIL PROTECTED]> writes: >> that a pure ANALYZE command needs only a read lock on the target table, >> not an exclusive lock as VACUUM needs, so it's much more friendly to >> concurrent transactions. > 7.1 already does the ANALYZE part of VACUUM ANALYZE with lighter > locking. Right, but you still have to run through the VACUUM part, which will hold down an exclusive lock for a considerable amount of time (if the table is big). regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
- [HACKERS] RFC: planner statistics in 7.2 Tom Lane
- Re: [HACKERS] RFC: planner statistics in 7.2y Bruce Momjian
- Re: [HACKERS] RFC: planner statistics in 7.2 Philip Warner
- Re: [HACKERS] RFC: planner statistics in 7.2 Tom Lane
- Re: [HACKERS] RFC: planner statistics in 7.2 Philip Warner
- Re: [HACKERS] RFC: planner statistics in 7.... Tom Lane
- Re: [HACKERS] RFC: planner statistics ... Philip Warner
- Re: [HACKERS] RFC: planner statist... Tom Lane
- Re: [HACKERS] RFC: planner sta... Philip Warner
- Re: [HACKERS] RFC: planner sta... Tom Lane
- Re: [HACKERS] RFC: planner sta... Hannu Krosing
- Re: [HACKERS] RFC: planner sta... Philip Warner