Re: monitoring CREATE INDEX [CONCURRENTLY]

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Rahila Syed <rahilasyed90(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: monitoring CREATE INDEX [CONCURRENTLY]
Date: 2019-02-13 02:59:27
Message-ID: CANP8+jJ9e4fv3NUcVgbgME6VhmSZLf42a8MD9yNCJNnNcXZe6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 13 Feb 2019 at 00:46, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> Here's a sample
> concurrent index build on a 100M tuple table.

Cool

> There are no concurrent
> transactions, so phases that wait for lockers don't appear.

Would prefer to see them, so we know they are zero.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2019-02-13 03:00:15 2019-02-14 Press Release Draft
Previous Message Shawn Debnath 2019-02-13 02:58:43 Re: Refactoring the checkpointer's fsync request queue