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

From: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
To: Vinayak Pokale <vinpokale(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-11 13:25:19
Message-ID: CADdR5nxbQG+7Uk4_YR3r+cYZ3PbbYTK--cNeLpAsGR=7cZMQkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Do you have more details about the failed tests?

Regards,
Remi

2017-05-06 5:38 GMT+02:00 Vinayak Pokale <vinpokale(at)gmail(dot)com>:

>
> 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-05-11 13:29:50 Re: If subscription to foreign table valid ?
Previous Message Robert Haas 2017-05-11 13:25:05 Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take)