Excerpts from Balamurugan Mahendran's message of lun nov 29 13:48:43 -0300 2010: > Thanks, I'll remove it. But I still get down time because of Vacuum(table > lock). Is there any other better way to do this? I don't mind to switch to > bigger instance with more Hardware.
I wonder if you're doing something other than INSERT/UPDATE/DELETE that causes the service to "block" in the presence of VACUUM. Maybe your application is trying to do ALTER TABLE too frequently (or something else entirely), which *would* block. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
