| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tomas Vondra <tv(at)fuzzy(dot)cz>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autovacuum stress-testing our system |
| Date: | 2012-09-27 09:51:28 |
| Message-ID: | CA+U5nMJMibhhnDf3sh+UzWE5RyniZrR0cuQaj=byjMpdJYUVyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26 September 2012 15:47, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> Really, as far as autovacuum is concerned, it would be much more useful
> to be able to reliably detect that a table has been recently vacuumed,
> without having to request a 10ms-recent pgstat snapshot. That would
> greatly reduce the amount of time autovac spends on pgstat requests.
VACUUMing generates a relcache invalidation. Can we arrange for those
invalidations to be received by autovac launcher, so it gets immediate
feedback of recent activity without polling?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-09-27 10:41:46 | Re: Re: [WIP] Performance Improvement by reducing WAL for Update Operation |
| Previous Message | Dimitri Fontaine | 2012-09-27 08:57:00 | Re: EVENT Keyword and CREATE TABLE |