| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jose Luis Tallon <jltallon(at)adv-solutions(dot)net> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: Thinking about EXPLAIN ALTER TABLE |
| Date: | 2018-12-11 13:51:39 |
| Message-ID: | 20181211135139.p4jgcblzdugffyzr@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Dec-11, Jose Luis Tallon wrote:
> * EXPLAIN PERFORM ALTER TABLE (EXPLAIN EXEC?) would explain + do
>
> ...and bonus points for explaining each step just before it is
> performed. This way, It'd be easy for users to verify that a particular step
> (i.e. table rewrite) is the one taking æons to run or hammering the storage.
We have a mechanism for reporting progress of DDL commands. Currently
as far as I remember it's able to report VACUUM progress; there's a
patch in commitfest to add support for CLUSTER. Rahila Syed in
https://www.pgcon.org/2017/schedule/attachments/472_Progress%20Measurement%20PostgreSQL.pdf
proposed ways to have it report for ALTER TABLE also, though I don't
think anyone has worked on that.
I think these two things are separate.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-12-11 14:15:16 | Re: Add timeline to partial WAL segments |
| Previous Message | maxzor | 2018-12-11 12:14:19 | Re: Patch for "CREATE TABLE ... (LIKE ... INCLUDING COMMENTS)" |