From: | Remi Colinet <remi(dot)colinet(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH v2] Progress command to monitor progression of long running SQL queries |
Date: | 2017-05-11 16:15:56 |
Message-ID: | CADdR5nx8CyUbJOnDoHe07CUyvbEPOX3T0=GsPXDCOtYRUZHDoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thx for your comment.
Based on other comments, I will probably convert the command into a SQL
function.
This allows passing arguments such as the one which can be used in the
current command (VERBOSE, FORMAT).
This will avoid keyword collisions.
Regards
Remi
2017-05-10 22:04 GMT+02:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hi
>
> 2017-05-10 18:40 GMT+02:00 Remi Colinet <remi(dot)colinet(at)gmail(dot)com>:
>
>> Hello,
>>
>> This is version 2 of the new command name PROGRESS which I wrote in order
>> to monitor long running SQL queries in a Postgres backend process.
>>
>
> This patch introduce lot of reserved keyword. Why? It can breaks lot of
> applications. Cannot you enhance EXPLAIN command?
>
> Regards
>
> Pavel
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2017-05-11 16:20:55 | Re: eval_const_expresisions and ScalarArrayOpExpr |
Previous Message | Remi Colinet | 2017-05-11 16:09:36 | Re: [PATCH v2] Progress command to monitor progression of long running SQL queries |