Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 6BA16633180 for ; Sun, 22 Aug 2010 11:04:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 21410-08 for ; Sun, 22 Aug 2010 14:04:19 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id 342A7633131 for ; Sun, 22 Aug 2010 11:04:21 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id o7ME49628565; Sun, 22 Aug 2010 10:04:09 -0400 (EDT) From: Bruce Momjian Message-Id: <201008221404.o7ME49628565@momjian.us> Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this? In-Reply-To: To: Rob Wultsch Date: Sun, 22 Aug 2010 10:04:09 -0400 (EDT) CC: Josh Berkus , Tom Lane , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/1598 X-Sequence-Number: 168401 Rob Wultsch wrote: > For a documentation patch should this not be back ported to all > relevant versions? It is only a minor adjustment and I normally don't backpatch that. --------------------------------------------------------------------------- > > On 8/21/10, Bruce Momjian wrote: > > Josh Berkus wrote: > >> > >> > On further reflection, though: since we put in the BufferAccessStrategy > >> > code, which was in 8.3, the background writer isn't *supposed* to be > >> > very much involved in writing pages that are dirtied by VACUUM. VACUUM > >> > runs in a small ring of buffers and is supposed to have to clean its own > >> > dirt most of the time. So it's wrong to blame this on the bgwriter not > >> > holding up its end. Rather, what you need to be thinking about is how > >> > come vacuum seems to be making lots of pages dirty on only one of these > >> > machines. > >> > >> This is an anti-wraparound vacuum, so it could have something to do with > >> the hint bits. Maybe it's setting the freeze bit on every page, and > >> writing them one page at a time? Still don't understand the call to > >> pollsys, even so, though. > > > > We often mention that we do vacuum freeze for anti-wraparound vacuum, > > but not for pg_clog file removal, which is the primary trigger for > > autovacuum vacuum freezing. I have added the attached documentation > > patch for autovacuum_freeze_max_age; back-patched to 9.0. > > > > -- > > Bruce Momjian http://momjian.us > > EnterpriseDB http://enterprisedb.com > > > > + It's impossible for everything to be true. + > > > > > -- > Rob Wultsch > wultsch@gmail.com -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +