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

From Pavel Stehule
Subject Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries
Date
Msg-id CAFj8pRDcbggZRdm7+8-hP=QwiRAmkH=JDtuUFkEod6HBGZMLjQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] [PATCH v2] Progress command to monitor progression of long runningSQL queries  (Remi Colinet <remi.colinet@gmail.com>)
Responses Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries  (Remi Colinet <remi.colinet@gmail.com>)
List pgsql-hackers
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: David Fetter
Date:
Subject: Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries
Next
From: Joe Conway
Date:
Subject: Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()