Re: [PATCH v2] Progress command to monitor progression of long running SQL queries

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Remi Colinet <remi(dot)colinet(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-10 20:04:53
Message-ID: CAFj8pRDcbggZRdm7+8-hP=QwiRAmkH=JDtuUFkEod6HBGZMLjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2017-05-10 20:09:36 Re: Should pg_current_wal_location() become pg_current_wal_lsn()
Previous Message David Fetter 2017-05-10 19:52:31 Re: [PATCH v2] Progress command to monitor progression of long running SQL queries