Re: [HACKERS] CLUSTER command progress monitor

From: Tattsu Yama <yamatattsu(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org, robertmhaas(at)gmail(dot)com
Cc: Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: [HACKERS] CLUSTER command progress monitor
Date: 2019-03-24 16:55:18
Message-ID: CAOKkKFv+kBeTVdHA0kzcoPJxZzDyAGUdftJDkqm3AHUM4xm1jA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Robert! >On Tue, Mar 19, 2019 at 2:47 PM Robert Haas
<robertmhaas(at)gmail(dot)com> wrote: >> how close you were getting to
rewriting the entire heap. This is the >> one thing I found but did not
fix; any chance you could make this >> change and update the documentation
to match? > > >Hi, is anybody working on this? Thank you so much for
reviewing the patch and sorry for the late reply. Today, I realized that
you sent the email for the patch because I took a sick leave from work for
a while. So, I created new patch based on your comments asap. I hope it is
acceptable to you. :) Please find attached file. Changes - Add new column
*heap_tuples_written* in the view This column is updated when the phases
are "seq scanning heap", "index scanning heap" or "writing new heap". - Fix
document - Revised the patch on 280a408b48d5ee42969f981bceb9e9426c3a344c

Regards,

Tatsuro Yamada

Attachment Content-Type Size
progress_monitor_for_cluster_command_v12.patch application/octet-stream 22.4 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2019-03-24 17:54:48 Re: warning to publication created and wal_level is not set to logical
Previous Message Andrey Borodin 2019-03-24 16:50:41 Re: GiST VACUUM