Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries
Date
Msg-id CAA4eK1LoRV4mnqX9GKBhi3gO_1AHGs5JAyK-gwpsKC2FR=z7SA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] [PATCH v2] Progress command to monitor progression of long runningSQL queries  (Remi Colinet <remi.colinet@gmail.com>)
Responses Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries  (Remi Colinet <remi.colinet@gmail.com>)
List pgsql-hackers
On Wed, May 10, 2017 at 10:10 PM, Remi Colinet <remi.colinet@gmail.com> wrote:
>
> Parallel queries can also be monitored. The same mecanism is used to monitor
> child workers with a slight difference: the main worker requests the child
> progression directly in order to dump the whole progress tree in shared
> memory.
>

What if there is any error in the worker (like "out of memory") while
gathering the statistics?  It seems both for workers as well as for
the main backend it will just error out.  I am not sure if it is a
good idea to error out the backend or parallel worker as it will just
end the query execution.  Also, even if it is okay, there doesn't seem
to be a way by which a parallel worker can communicate the error back
to master backend, rather it will just exit silently which is not
right.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Hash Functions