pgsql: Fix logging of pages skipped due to pins during vacuum.

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix logging of pages skipped due to pins during vacuum.
Date: 2015-01-08 12:18:00
Message-ID: E1Y9C2K-0004Rv-83@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix logging of pages skipped due to pins during vacuum.

The new logging introduced in 35192f06 made the incorrect assumption
that scan_all vacuums would always wait for buffer pins; but they only
do so if the page actually needs to be frozen.

Fix that inaccuracy by removing the difference in log output based on
scan_all and just always remove the same message. I chose to keep the
split log message from the original commit for now, it seems likely
that it'll be of use in the future.

Also merge the line about buffer pins in autovacuum's log output into
the existing "pages: ..." line. It seems odd to have a separate line
about pins, without the "topic: " prefix others have.

Also rename the new 'pinned_pages' variable to 'pinskipped_pages'
because it actually tracks the number of pages that could *not* be
pinned.

Discussion: 20150104005324(dot)GC9626(at)awork2(dot)anarazel(dot)de

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/17eaae9897781c6dcc622b9327899329e4d2a4df

Modified Files
--------------
src/backend/commands/vacuumlazy.c | 32 ++++++++------------------------
1 file changed, 8 insertions(+), 24 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2015-01-08 12:39:08 pgsql: Protect against XLogReaderAllocate() failing to allocate memory.
Previous Message Noah Misch 2015-01-08 04:06:06 pgsql: On Darwin, detect and report a multithreaded postmaster.