pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedNew autovacuum messages in postgres log after upgrade
2+ messages / 2 participants
[nested] [flat]
* New autovacuum messages in postgres log after upgrade
@ 2013-09-17 03:32 Benjamin Krajmalnik <kraj@servoyant.com>
2013-09-17 15:19 ` Re: New autovacuum messages in postgres log after upgrade Kevin Grittner <kgrittn@ymail.com>
0 siblings, 1 reply; 2+ messages in thread
From: Benjamin Krajmalnik @ 2013-09-17 03:32 UTC (permalink / raw)
To: pgsql-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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: New autovacuum messages in postgres log after upgrade
2013-09-17 03:32 New autovacuum messages in postgres log after upgrade Benjamin Krajmalnik <kraj@servoyant.com>
@ 2013-09-17 15:19 ` Kevin Grittner <kgrittn@ymail.com>
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Grittner @ 2013-09-17 15:19 UTC (permalink / raw)
To: Benjamin Krajmalnik <kraj@servoyant.com>; pgsql-admin
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.
>
> 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?
Yes, table truncation after a large number of deletes is now
smarter, getting more done with less effort and blocking. This
message, which was useful for developing the fix, made it into
production at the LOG level. In the next minor release it will be
changed to the DEBUG level to avoid cluttering the log with entries
about routine activities.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2013-09-17 15:19 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-09-17 03:32 New autovacuum messages in postgres log after upgrade Benjamin Krajmalnik <kraj@servoyant.com>
2013-09-17 15:19 ` Kevin Grittner <kgrittn@ymail.com>
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