| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | "Hannu Krosing" <hannu(at)2ndquadrant(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feedback on getting rid of VACUUM FULL |
| Date: | 2009-09-16 23:31:40 |
| Message-ID: | 4AB12F0C020000250002B20C@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I think this should be in core, not a contrib module.
+1
> I also wonder whether we should consider teaching regular VACUUM to
> do a little of this every time it's run. Right now, once your table
> gets bloated, it stays bloated forever, until you intervene. Making
> it slowly get better by itself would reduce the number of people who
> live with the problem for a month or a year before writing in to say
> "Access to this table seems really slow...".
+1 if feasible. That would be a very nice feature.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-16 23:32:01 | Re: Hot Standby 0.2.1 |
| Previous Message | Emmanuel Cecchet | 2009-09-16 22:43:39 | Re: generic copy options |