Horton

Re: BUG #14057: vacuum setting reltuples=0 for tables with >0 tuples

Andrew Gierth <andrew@tao11.riddles.org.uk>

View thread View on postgr.es
From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: pgsql-bugs@postgresql.org
Cc: Andres Freund <andres@anarazel.de>
Date: 2017-03-16T06:55:54Z
Lists: pgsql-bugs

Attachments

>>>>> "Andres" == Andres Freund <andres@anarazel.de> writes:

 >> It looks like fixing this requires breaking scanned_pages out into
 >> at least two separate counters, since we currently use it to track
 >> both whether we can update stats, and whether we can update
 >> relfrozenxid.

 Andres> Are you planning to submit a fix?

Somewhat belatedly, yes.

Attached are patches against master and all the back branches back to
9.2.  I've reproduced the bug on all of them, and confirmed that this
fixes it on all of them.  Is it worth also including the isolation
tester script in the changes?

I can go ahead and commit these if they look ok.

-- 
Andrew (irc:RhodiumToad)

Commits

  1. Avoid having vacuum set reltuples to 0 on non-empty relations in the