Re: Proposal: Log inability to lock pages during vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: Log inability to lock pages during vacuum
Date: 2014-12-18 20:50:31
Message-ID: 3172.1418935831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Great, thanks, pushed. I tweaked it a bit more, so that it would say
> either "skipped N pages" or "waited N pins" in both autovacuum and
> vacuum verbose cases, but only if N > 0.

Not directly relevant but ... I think probably all those BlockNumber
counters should be printed with %u not %d. A relation with between
2G and 4G pages is possible, and it wouldn't look right with %d.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-12-18 20:55:05 Re: Proposal: Log inability to lock pages during vacuum
Previous Message Alvaro Herrera 2014-12-18 20:21:36 Re: Proposal: Log inability to lock pages during vacuum