That's good point. I will probably convert the new command to a SQL function.
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. Regards Remi 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? > > 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 >
