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

From: David Fetter <david(at)fetter(dot)org>
To: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH v2] Progress command to monitor progression of long running SQL queries
Date: 2017-05-10 19:52:31
Message-ID: 20170510195231.GB12623@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 10, 2017 at 06:40:31PM +0200, Remi Colinet wrote:
> 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.

Perhaps I missed something important in the discussion, but was there
a good reason that this isn't a function callable from SQL, i.e. not
restricted to the psql client?

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-05-10 20:04:53 Re: [PATCH v2] Progress command to monitor progression of long running SQL queries
Previous Message Robert Haas 2017-05-10 19:52:23 Re: Issues with replication slots(which created manually) against logical replication