Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VLm1u-00084L-OB for pgsql-admin@arkaria.postgresql.org; Tue, 17 Sep 2013 03:32:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VLm1t-0005m0-Bl for pgsql-admin@arkaria.postgresql.org; Tue, 17 Sep 2013 03:32:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VLm1s-0005lt-8v for pgsql-admin@postgresql.org; Tue, 17 Sep 2013 03:32:44 +0000 Received: from p01c11o148.mxlogic.net ([208.65.144.71]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VLm1o-0000BV-1I for pgsql-admin@postgresql.org; Tue, 17 Sep 2013 03:32:43 +0000 Received: from unknown [64.207.29.137] (EHLO mail.illumen.com) by p01c11o148.mxlogic.net(mxl_mta-7.1.0-4) with ESMTP id 45dc7325.0.131690.00-182.347137.p01c11o148.mxlogic.net (envelope-from ); Mon, 16 Sep 2013 21:32:39 -0600 (MDT) X-MXL-Hash: 5237cd57045e4ea7-ad983bbc43c9047558be644cdc9cb94aa4cb00fd X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CEB356.8DAD1942" Subject: New autovacuum messages in postgres log after upgrade Date: Mon, 16 Sep 2013 21:32:34 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New autovacuum messages in postgres log after upgrade Thread-Index: Ac6zVTFsvrX5SUrESrKd8Z4S7UAg7A== From: "Benjamin Krajmalnik" To: X-AnalysisOut: [v=2.0 cv=IKK1/HTG c=1 sm=1 a=1OfdrSViP1MTJkE3a0EXnQ==:17 a] X-AnalysisOut: [=UuVbNIZGTxAA:10 a=ck15eWJVN7kA:10 a=BLceEmwcHowA:10 a=k_T] X-AnalysisOut: [MK0BoAAAA:8 a=xMi_yRNoz4gA:10 a=Pp9p-WAGo2ejssn66K8A:9 a=C] X-AnalysisOut: [juIK1q_8ugA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=LQoquAa] X-AnalysisOut: [E0enVmpPI_7wA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZe] X-AnalysisOut: [C7Yk6K0A:10 a=frz4AuCg-hUA:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SOURCE-IP: [64.207.29.137] X-Pg-Spam-Score: -3.5 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CEB356.8DAD1942 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: automatic vacuum of table "ishield.public.tbltmptests": could not (re)acquire exclusive lock for truncate scan 2013-09-16 21:15:59 MDT LOG: automatic vacuum of table "ishield.public.tbltmptests": could not (re)acquire exclusive lock for truncate scan 2013-09-16 21:16:00 MDT LOG: 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? I did notice that while previously I had issues with vacuum full not being able to run due to not finding an entry in toast tables, this appears to have been resolved. =20 Thanks in advance, =20 Benjamin =20 ------_=_NextPart_001_01CEB356.8DAD1942 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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.

 

2013-09-16 21:15:58 MDT LOG:  automatic vacuum of = table "ishield.public.tbltmptests": could not (re)acquire = exclusive lock for truncate scan

2013-09-16 21:15:59 MDT LOG:  automatic vacuum of = table "ishield.public.tbltmptests": could not (re)acquire = exclusive lock for truncate scan

2013-09-16 21:16:00 MDT LOG:  automatic vacuum of = table "ishield.public.tbltmptests": could not (re)acquire = exclusive lock for truncate scan

 

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?

I did notice that while = previously I had issues with vacuum full not being able to run due to = not finding an entry in toast tables, this appears to have been = resolved.

 

Thanks in advance,

 

Benjamin

 

------_=_NextPart_001_01CEB356.8DAD1942--