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 <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-bugs by date
|Next:||From: David Quinn-Jacobs||Date: 2010-11-29 19:11:19|
|Subject: BUG #5775: DBLINK Connection String Truncation|
|Previous:||From: Tom Lane||Date: 2010-11-29 18:27:38|
|Subject: Re: BUG #5761: In 'dblink' function connection string truncated |