On 5 May 2017 at 22:38, Vinayak Pokale <[email protected]> wrote: > > On Mon, Apr 17, 2017 at 9:09 PM, Remi Colinet <[email protected]> > wrote: >> >> Hello, >> >> I've implemented a new command named PROGRESS to monitor progression of >> long running SQL queries in a backend process. >> > Thank you for the patch. >
sorry if i'm bikeshedding to soon but... why a command instead of a function? something like pg_progress_backend() will be in sync with pg_cancel_backend()/pg_terminate_backend() and the result of such a function could be usable by a tool to examine a slow query status -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
