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>, Andres Freund <andres@anarazel.de>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers@postgresql.org
Date: 2020-01-21T20:54:59Z
Lists: pgsql-hackers 
On 2020-Jan-21, Justin Pryzby wrote:

> On Tue, Jan 21, 2020 at 03:11:35PM +0900, Masahiko Sawada wrote:
> > Some of them conflicts with the current HEAD(62c9b52231). Please rebase them.
> 
> Sorry, it's due to other vacuum patch in this branch.
> 
> New patches won't conflict, except for the 0005, so I renamed it for cfbot.
> If it's deemed to be useful, I'll make a separate branch for the others.

I think you have to have some other patches applied before these,
because in the context lines for some of the hunks there are
double-slash comments.

-- 
Á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