| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Balamurugan Mahendran <balamurugan(at)adaptavant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, depesz <depesz(at)depesz(dot)com>, Bala Murugan <b2m(at)a-cti(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5774: VACCUM & REINDEX kills production environement |
| Date: | 2010-11-29 18:53:36 |
| Message-ID: | 1291056710-sup-3907@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Quinn-Jacobs | 2010-11-29 19:11:19 | BUG #5775: DBLINK Connection String Truncation |
| Previous Message | Tom Lane | 2010-11-29 18:27:38 | Re: BUG #5761: In 'dblink' function connection string truncated |