| From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
|---|---|
| To: | Vinayak Pokale <vinpokale(at)gmail(dot)com> |
| Cc: | Remi Colinet <remi(dot)colinet(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] New command to monitor progression of long running queries |
| Date: | 2017-05-06 03:57:03 |
| Message-ID: | CAJGNTePVzgYNdTk7YSCuBKDHTfWZghrbkKHcP8BGV0E_ury9YA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 May 2017 at 22:38, Vinayak Pokale <vinpokale(at)gmail(dot)com> wrote:
>
> On Mon, Apr 17, 2017 at 9:09 PM, Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
> wrote:
>>
>> Hello,
>>
>> I've implemented a new command named PROGRESS to monitor progression of
>> long running SQL queries in a backend process.
>>
> Thank you for the patch.
>
sorry if i'm bikeshedding to soon but... why a command instead of a function?
something like pg_progress_backend() will be in sync with
pg_cancel_backend()/pg_terminate_backend() and the result of such a
function could be usable by a tool to examine a slow query status
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2017-05-06 05:33:24 | Re: delta relations in AFTER triggers |
| Previous Message | Vinayak Pokale | 2017-05-06 03:38:38 | Re: [PATCH] New command to monitor progression of long running queries |