pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Benjamin Krajmalnik <kraj@servoyant.com>
To: pgsql-admin@postgresql.org
Subject: New autovacuum messages in postgres log after upgrade
Date: Mon, 16 Sep 2013 21:32:34 -0600
Message-ID: <F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

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

 

view thread (2+ messages)  latest in thread

Message-ID: <F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local>
Permalink:  ../F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local/
Also on:    postgresql.org/message-id/F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: kraj@servoyant.com
  Subject: Re: New autovacuum messages in postgres log after upgrade
  In-Reply-To: <F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local>
  References: <F4E6A2751A2823418A21D4A160B68988C2E3D4@fletch.stackdump.local>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox