Re: Autovacuum different in 9.2.4?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Autovacuum different in 9.2.4?
Date: 2013-08-05 19:35:47
Message-ID: 51FFFE93.8010503@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 08/05/2013 12:13 PM, Jeff Janes wrote:
>
> On Mon, Aug 5, 2013 at 11:16 AM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>>
>> Hello,
>>
>> I seem to recall autovacuum changes landing for 9.2.4. Can someone please
>> describe what those changes were and how they could affect usage?
>
> Those landed in 9.2.3, see release notes for that version:
> Fix performance problems with autovacuum truncation in busy workloads
> (Jan Wieck)
> Fix error in vacuum_freeze_table_age implementation (Andres Freund)
>
> There should be no change in usage, unless you were taking some heroic
> methods to overcome the problems and can now discontinue them.

That is what is confusing me, I could be cracked but messages like these:

automatic vacuum of table "pg_catalog.pg_attribute": could not
(re)acquire exclusive lock for truncate scan

Seem to be new?

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Atri Sharma 2013-08-05 19:36:20 Moving 'hot' pages from buffer pool to heap
Previous Message Kevin Grittner 2013-08-05 19:32:24 Re: Autovacuum different in 9.2.4?