| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Scott Carey <scott(at)richrelevance(dot)com> |
| Cc: | Janet Jacobsen <jsjacobsen(at)lbl(dot)gov>, Marcin Stępnicki <mstepnicki(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: slow DELETE on 12 M row table |
| Date: | 2009-06-28 02:09:36 |
| Message-ID: | 603c8f070906271909t2d168d2ft94717cc95a497197@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2009/6/27 Scott Carey <scott(at)richrelevance(dot)com>:
> In addition to the above, note that long lived transactions cause all sorts
> of other problems in the database. In particular, table and index bloat can
> become severe due to this sort of poor client behavior if there is a lot of
> update or delete activity. You can find out with "vacuum analyze verbose"
> on tables of interest whether there are a high ratio of dead tuples in the
> tables and indexes.
Yes indeed... by the by, I understand Alvaro Herrera has improved
this situation considerably for the forthcoming 8.4 release.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alan McKay | 2009-06-28 13:52:24 | Re: what server stats to track / monitor ? |
| Previous Message | Greg Smith | 2009-06-27 05:08:17 | Re: Insert performance and multi-column index order |