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

That's a good point. A command is more straightforward because it targets only one backend. The user is supposed to know which backend pid is taking a long time to complete based on pg_stat_activity(). This is somehow the same approach as EXPLAIN command. But the use is limited to psql utility.

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

Do you have more details about the failed tests? Regards, Remi 2017-05-06 5:38 GMT+02:00 Vinayak Pokale : > > On Mon, Apr 17, 2017 at 9:09 PM, Remi Colinet > wrote: > >> Hello, >> >> I've implemented a new command named PROGRESS to monitor

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

On 5 May 2017 at 22:38, Vinayak Pokale wrote: > > On Mon, Apr 17, 2017 at 9:09 PM, Remi Colinet > wrote: >> >> Hello, >> >> I've implemented a new command named PROGRESS to monitor progression of >> long running SQL queries in a backend process. >> >

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

On Mon, Apr 17, 2017 at 9:09 PM, Remi Colinet 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

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

2017-04-19 18:41 GMT+02:00 Maksim Milyutin : > On 19.04.2017 17:13, Remi Colinet wrote: > >> Maksim, >> >> >> 2017-04-18 20:31 GMT+02:00 Maksim Milyutin > >: >> >> On 18.04.2017 17:39, Remi Colinet wrote:

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

On 19.04.2017 17:13, Remi Colinet wrote: Maksim, 2017-04-18 20:31 GMT+02:00 Maksim Milyutin >: On 18.04.2017 17:39, Remi Colinet wrote: Regarding the queryDesc state of SQL query upon receiving a request to

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

Following on previous email I have added below some use cases which I find very relevant when we need to know the progress of a SQL query. The command can be used by any SQL query (select, update, delete, insert). The tables used have been created with : CREATE TABLE T_1M (id integer, md5

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

Maksim, 2017-04-18 20:31 GMT+02:00 Maksim Milyutin : > On 18.04.2017 17:39, Remi Colinet wrote: > >> Hello Maksim, >> >> The core implementation I suggested for the new PROGRESS command uses >> different functions from the one used by EXPLAIN for its core >>

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

On 18.04.2017 17:39, Remi Colinet wrote: Hello Maksim, The core implementation I suggested for the new PROGRESS command uses different functions from the one used by EXPLAIN for its core implementation. Some source code is shared with EXPLAIN command. But this shared code is only related to

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

Hello Maksim, The core implementation I suggested for the new PROGRESS command uses different functions from the one used by EXPLAIN for its core implementation. Some source code is shared with EXPLAIN command. But this shared code is only related to quals, properties, children, subPlans and few

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

Hi! On 17.04.2017 15:09, Remi Colinet wrote: Hello, I've implemented a new command named PROGRESS to monitor progression of long running SQL queries in a backend process. Use case === A use case is shown in the below example based on a table named t_10m with 10 millions rows. The table