Horton

Re: error context for vacuum to include block number

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>, Amit Kapila <amit.kapila16@gmail.com>, Andres Freund <andres@anarazel.de>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers@postgresql.org
Date: 2020-03-27T00:41:21Z
Lists: pgsql-hackers 
On 2020-Mar-26, Justin Pryzby wrote:

> On Thu, Mar 26, 2020 at 07:49:51PM -0300, Alvaro Herrera wrote:

> > BTW I'm pretty sure this "revert back" phrasing is not good English --
> > you should just use "revert".  Maybe get some native speaker's opinion
> > on it.
> 
> I'm a native speaker; "revert back" might be called redundant but I think it's
> common usage.

Oh, okay.

> > And speaking of language, I find the particle "cbarg" rather very ugly,
> 
> I renamed it since it was kind of opaque looking.  It's in all the same places,
> so equally infectious; but I hope you like it better.

I like it much better, thanks :-)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Avoid calls to RelationGetRelationName() and RelationGetNamespace() in

  2. Introduce vacuum errcontext to display additional information.

  3. Fix mesurement of elapsed time during truncating heap in VACUUM.

  4. Allow vacuum command to process indexes in parallel.

  5. Refactor code dedicated to index vacuuming in vacuumlazy.c

  6. Remove duplicated progress reporting during heap scan of VACUUM