Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews and approves it. --------------------------------------------------------------------------- Simon Riggs wrote: > On Thu, 2007-03-08 at 14:53 -0300, Alvaro Herrera wrote: > > Maybe something like this is better: > > > > LOG: index passes: 1 pages: removed 0, 197 remain tuples: removed 7199, > > 2338 remain CPU usage: whatever > > CONTEXT: Automatic vacuuming of table "database.public.w" > > Yours is better. > > I've implemented this: > > LOG: autovac "public.w" index passes: 1 pages: removed 0, 197 remain > tuples: removed 7199, 2338 remain CPU usage: whatever > > I'm happy if this gets removed later, but I think it will help everybody > understand how multi-vacuums are working and what the best way to > specify the controls should be. > > Not sure about the CONTEXT bit. I think its verbose, plus I thought that > was for ERRORs only. I will defer on this point, since I know y'all > understand that better than I. > > -- > Simon Riggs > EnterpriseDB http://www.enterprisedb.com > [ Attachment, skipping... ] > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq