On Thu, May 11, 2017 at 05:24:16PM +0200, Remi Colinet wrote: > 2017-05-10 21:52 GMT+02:00 David Fetter <da...@fetter.org>: > > > 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?
Please don't top post. http://www.caliburn.nl/topposting.html > That's good point. > > I will probably convert the new command to a SQL function. Great! > I was fumbling between a table or a SQL function. Oracle uses > v$session_longops to track progression of long running SQL queries > which have run for more than 6 seconds. But a function is much > better to provide parameters such as the backend pid and a format > specification for the output. Once it's a function, it can very easily be called in a system (or user-defined) view. 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
