From: | Sameer Thakur <samthakur74(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
Date: | 2015-07-02 05:21:51 |
Message-ID: | 1435814511411-5856192.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
>Thank you for suggestion. The design with hooks and a separate view was
mainly to keep most of the >code outside core as the feature proposed is
specific to VACUUM command. Also, having a separate view >can give more
flexibility in terms of displaying various progress parameters.
>FWIW ,there was resistance to include columns in pg_stat_activity earlier
in the following thread,
>http://www.postgresql.org/message-id/AANLkTi=TcuMA38oGUKX9p5WVPpY+M3L0XUp7=PLT+LCT@...
Perhaps as suggested in the link, the progress could be made available via a
function call which does progress calculation "on demand". Then we do not
need a separate view, or clutter pg_stat_activity, and also has benefit of
calculating progress just when it's needed.
--
View this message in context: http://postgresql.nabble.com/PROPOSAL-VACUUM-Progress-Checker-tp5855849p5856192.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2015-07-02 05:26:27 | Re: [PROPOSAL] VACUUM Progress Checker. |
Previous Message | Kouhei Kaigai | 2015-07-02 05:21:39 | Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API) |