Re: [PATCH] New command to monitor progression of long running queries

From: Vinayak Pokale <vinpokale(at)gmail(dot)com>
To: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] New command to monitor progression of long running queries
Date: 2017-05-06 03:38:38
Message-ID: CAEySZvggX7XwZy4cWv4rag7oyri-rHSDCkXmxNWxZw7cVW-Ckg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 17, 2017 at 9:09 PM, Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
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.

I am testing your patch but after applying your patch other regression test
failed.

$ make installcheck
13 of 178 tests failed.

Regards,
Vinayak

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2017-05-06 03:57:03 Re: [PATCH] New command to monitor progression of long running queries
Previous Message Stephen Frost 2017-05-06 03:28:18 Re: pg_dump emits ALTER TABLE ONLY partitioned_table