Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries - Mailing list pgsql-hackers

From Remi Colinet
Subject Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries
Date
Msg-id CADdR5nx8CyUbJOnDoHe07CUyvbEPOX3T0=GsPXDCOtYRUZHDoQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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.stehule@gmail.com>:
Hi

2017-05-10 18:40 GMT+02:00 Remi Colinet <remi.colinet@gmail.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


pgsql-hackers by date:

Previous
From: Remi Colinet
Date:
Subject: Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] eval_const_expresisions and ScalarArrayOpExpr