From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Displaying accumulated autovacuum cost |
Date: | 2011-10-05 11:43:54 |
Message-ID: | 1317815012-sup-9022@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Greg Smith's message of mié oct 05 04:02:12 -0300 2011:
>
> On 09/29/2011 10:40 AM, Alvaro Herrera wrote:
> > I reviewed this patch. My question for you is: does it make sense to
> > enable to reporting of write rate even when vacuum cost accounting is
> > enabled? In my opinion it would be useful to do so. If you agree,
> > please submit an updated patch.
>
> Presumably you meant to ask if this makes sense to show when cost
> accounting isn't enabled, because the code doesn't do that right now.
> No cost accounting, no buffer usage/write rate data as this was submitted.
Yes, sorry, that's what I meant.
> Looks like making this work even in cases where cost accounting isn't on
> will make the patch a bit larger obtrusive, but it's not unreasonable.
> Now that you mention it, people who do a manual, full-speed VACUUM would
> certainly appreciate some feedback on the rate it ran at. I'll include
> that in the next update.
Thanks.
--
Á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 | Pavel Stehule | 2011-10-05 12:33:29 | Re: [REVIEW] prepare plans of embedded sql on function start |
Previous Message | Hamza Bin Sohail | 2011-10-05 09:16:00 | Query regarding postgres lock contention - Followup |