Re: Logging pg_autovacuum
От | Larry Rosenman |
---|---|
Тема | Re: Logging pg_autovacuum |
Дата | |
Msg-id | F6616E0E81AC0841B1F9DD252F7C4B55041A51@ausmaildd.aus.pervasive.com обсуждение исходный текст |
Ответ на | Logging pg_autovacuum (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | pgsql-hackers |
Simon Riggs wrote: > On Fri, 2006-04-28 at 22:38 +0200, Martijn van Oosterhout wrote: >> On Fri, Apr 28, 2006 at 03:18:56PM -0500, Larry Rosenman wrote: >>>> Martijn van Oosterhout <kleptog@svana.org> writes: >>>>> You know, rather than adding new columns to pg_class, why not >>>>> extend the stats collector to collect this information. >>> >>> That sounds doable. And a lot less scary for me (as a relative >>> noobie) to do. >> >> Well, I've been thinking a bit more and it seems a perfect fit in >> many ways. None of the info we're talking about here takes any extra >> time to calculate, it's all debates about what to log. So send it to >> the stats collector and let it deal with it. >> >> It should probably tie in with normal vacuum. We get requests from >> time to time from people wanting to know the last time a table was >> vacuumed (not autovacuumed) for example. > > Good idea; Agreed. I've done this (collecting the data), and actually what I have is BOTH, last vacuum and last autovacuum, as well as last analyze and last autovacuum analyze. Do folks want both, or is just one sufficient. I posted a WIP patch yesterday that just does the collection and storage, but not added the columns to the views. I'm planning on doing the view stuff and docs today. Comments/feedback welcome. LER -- Larry Rosenman Database Support Engineer PERVASIVE SOFTWARE. INC. 12365B RIATA TRACE PKWY 3015 AUSTIN TX 78727-6531 Tel: 512.231.6173 Fax: 512.231.6597 Email: Larry.Rosenman@pervasive.com Web: www.pervasive.com
В списке pgsql-hackers по дате отправления: