Re: autovacuum and transaction id wraparound

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: pawel_kukawski <kukismen(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: autovacuum and transaction id wraparound
Date: 2012-03-09 16:22:36
Message-ID: CAOR=d=1PxhwzQ4tuYniX_ZioG9KGYC1n2PJFYgt4+MtcdYPrYQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Mar 9, 2012 at 12:15 AM, pawel_kukawski <kukismen(at)gmail(dot)com> wrote:
> Hi Jens,
>
> Thanks for answer. One more question:
>
> Can the manual VACUUM operate on database where there are long lasting
> transactions?
>
> In other words, do I need to restart the server or kill long lasting
> transactions in order to allow manual VACUUM to clear old XIDs?

Long running transactions block both manual and automatic vacuums.

The only difference between manual and automatic vacuuming is the
costing parameters, which don't have to be different. I.e. if you set
the autovacuum_* costs to the same as the vacuum_* costs no diff in
operation.

The issue you might run into is the one Tom mentioned, that if you've
got a long running autovacuum that started with the older less
aggressive settings you might need to kill it (you can use
pg_cancel_backend() or sigint from the command like) to get it to
start back up with the new costs.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bret Stern 2012-03-09 16:53:25 Regarding NOTIFY
Previous Message Andy Colson 2012-03-09 16:19:54 Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?