Re: vac truncation scan problems - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: vac truncation scan problems
Date
Msg-id CAB7nPqTMBd6=5i3ZOg9t6A0km4VZ=wNt4_rwOzPVm683-aQ=Qw@mail.gmail.com
Whole thread Raw
In response to Re: vac truncation scan problems  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: vac truncation scan problems
List pgsql-hackers


On Wed, Apr 1, 2015 at 2:18 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
On Tue, Mar 31, 2015 at 1:28 AM, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote:
Hi, this is a bug in the commit 0d831389749a3baaced7b984205b9894a82444b9 .

It allows vucuum freeze to be skipped and inversely lets regular
vacuum wait for lock. The attched patch fixes it.


In table_recheck_autovac, vacuum options are determined as following,

 >      tab->at_vacoptions = VACOPT_SKIPTOAST |
 >              (dovacuum ? VACOPT_VACUUM : 0) |
 >              (doanalyze ? VACOPT_ANALYZE : 0) |
!>              (wraparound ? VACOPT_NOWAIT : 0);

The line prefixed by '!' looks inverted.

Thanks, it is obvious once you see it!

Nice catch, Horiguchi-san.
--
Michael

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: libpq's multi-threaded SSL callback handling is busted
Next
From: Craig Ringer
Date:
Subject: pg_restore -t should match views, matviews, and foreign tables