| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Henrik <henke(at)mac(dot)se> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Nested loop in simple query taking long time |
| Date: | 2007-12-06 19:26:28 |
| Message-ID: | 20071206192628.GJ8451@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Henrik wrote:
> I think I have a clue why its so off. We update a value in that table about
> 2 - 3 million times per night and as update creates a new row it becomes
> bloated pretty fast. The table hade a size of 765 MB including indexes and
> after vacuum full and reindex it went down to 80kB... I guess I need
> routine reindex on this table. Thank god is not big. :)
I suggest you put a lone VACUUM on that table in cron, say once every 5
minutes, and you should be fine. You shouldn't need a reindex at all.
--
Alvaro Herrera http://www.PlanetPostgreSQL.org/
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended." (Gerry Pourwelle)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Wells | 2007-12-06 19:35:42 | Re: Recovering data via raw table and field separators |
| Previous Message | Weber, Geoffrey M. | 2007-12-06 19:22:30 | Continual Postgres headaches... |