Vacuum now uses AccessShareLock for analyze

I have changed vacuum so analyze now uses AccessShareLock. (Is this the
proper lock for analyze?)

The code will now vacuum all requested relations. It will then analyze
each relation. This way, all the exclusive vacuum work is done first,
then analyze can continue with shared locks.

The code is much clearer with that functionality split into separate
functions.

How separate do people want vacuum and analyze? Analyze currently does
not record the number of tuples and pages, because vacuum does that. Do
people want analyze as a separate command and in a separate file?

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026