Neil, Thanks for the good advice. I noticed that I had some sessions for which I could not account, and I think even a 2nd postmaster running. It looks like I've cleaned everything up, and now I can VACUUM and I can DROP an index which wouldn't drop.
And I'm looking into upgrading PostgreSQL. -David On Tuesday, December 16, 2003 2:51 PM, Neil Conway [SMTP:[EMAIL PROTECTED] wrote: > "David Shadovitz" <[EMAIL PROTECTED]> writes: > > I'm running PG 7.2.2 on RH Linux 8.0. > > Note that this version of PostgreSQL is quite old. > > > I'd like to know why "VACUUM ANALYZE <table>" is extemely slow (hours) for > > certain tables. > > Is there another concurrent transaction that has modified the table > but has not committed? VACUUM ANALYZE will need to block waiting for > it. You might be able to get some insight into this by examining the > pg_locks system view: > > http://www.postgresql.org/docs/current/static/monitoring-locks.html > > As well as the pg_stat_activity view. > > -Neil ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
