Jaromír Talíř wrote:
> we are facing strange situation with exclusively locked table during
> normal lazy vacuum. There is one big table (66GB) that is heavily
> inserted and updated in our database. Suddenly (after backup and delete
> of almost all records) we are not able to run VACUUM over this table
> because after 50 minutes of work it allocate AccessExclusiveLock on this
> table and all other connections start to timeout.
What version are you running?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.