DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com;
 h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
 b=g0lpdlvUnKcaKpcBg2vfrwCtyYswXZ0pQpJJjrIDwNCYQ2TpG26Imd65JeNvH/NnJ24yL9CuRRiIRIHZIq38kYnuxgjGL6OsZKPzQbv3fe0pEgJKWTi/na5xgDxrJjV2c8UfWT7SLmODy5hFh2mmbXN1y99VHeQ6FmzBaoxExs8=;
References: <F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local>
Message-ID: <1379431174.27898.YahooMailNeo@web162902.mail.bf1.yahoo.com>
Date: Tue, 17 Sep 2013 08:19:34 -0700 (PDT)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: New autovacuum messages in postgres log after upgrade
To: Benjamin Krajmalnik <kraj@servoyant.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Benjamin Krajmalnik <kraj@servoyant.com> wrote:

> During a maintenance window, we upgraded our systems to Postgres
> 9.0.13 from 9.0.3 running on FreeBSD 8.1 amd64.
> When we restarted the postgres server, I notices, and continue to
> notice, a recurrence of messages in the log.
>=20
> 2013-09-16 21:15:58 MDT LOG:=A0 automatic vacuum of table "ishield.public=
.tbltmptests": could not (re)acquire exclusive lock for truncate scan
> 2013-09-16 21:15:59 MDT LOG:=A0 automatic vacuum of table "ishield.public=
.tbltmptests": could not (re)acquire exclusive lock for truncate scan
> 2013-09-16 21:16:00 MDT LOG:=A0 automatic vacuum of table "ishield.public=
.tbltmptests": could not (re)acquire exclusive lock for truncate scan
>=20
> The tables on which I am seeing this messages are essentially
> temporary work tables into which we insert records, which are
> processed by triggers, and then deleted.
> Performance of the system does not seem to have been affected by
> the upgrade.
> Is this simply caused by a higher level of verbosity in the
> autovaccum logging, as a result of the autovacuum fix in 9.0.12?

Yes, table truncation after a large number of deletes is now
smarter, getting more done with less effort and blocking.=A0 This
message, which was useful for developing the fix, made it into
production at the LOG level.=A0 In the next minor release it will be
changed to the DEBUG level to avoid cluttering the log with entries
about routine activities.

--=20
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin