Horton

Re: monitoring CREATE INDEX [CONCURRENTLY]

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Rahila Syed <rahila.syed@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Pg Hackers <pgsql-hackers@lists.postgresql.org>, David Fetter <david@fetter.org>, Pavan Deolasee <pavan.deolasee@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Date: 2019-04-06T04:40:42Z
Lists: pgsql-hackers 
On 2019-Apr-05, Peter Eisentraut wrote:

> I've reworded the phases a bit.  There was a bit of a mixup of waiting
> for snapshots and waiting for lockers.  Perhaps not so important from a
> user's perspective, but at least now it's more consistent with the
> source code comments.

No disagreement with that.  Looks reasonable.

I didn't test the patch, but it seems OK in a quick once-over.

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

Commits

  1. Report progress of REINDEX operations

  2. Report progress of CREATE INDEX operations

  3. Fix error handling of readdir() port implementation on first file lookup