Re: On-demand running query plans using auto_explain and signals - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: On-demand running query plans using auto_explain and signals
Date
Msg-id CAFj8pRAfA1qOQn8Rqc7JNPDK3OKq8wH==7Y9JwE25gYFWW9uEw@mail.gmail.com
Whole thread Raw
In response to Re: On-demand running query plans using auto_explain and signals  (Andres Freund <andres@anarazel.de>)
Responses Re: On-demand running query plans using auto_explain and signals
List pgsql-hackers


2015-08-29 18:36 GMT+02:00 Andres Freund <andres@anarazel.de>:
On 2015-08-29 18:27:59 +0200, Pavel Stehule wrote:
> 2015-08-29 18:25 GMT+02:00 Shulgin, Oleksandr <oleksandr.shulgin@zalando.de>
> > Good point.  There's still hope to set a flag and process it later on.
> > Will have to check if it's possible to stay in the scope of a loaded module
> > though.

> I had a workable prototype - and It was implemented very similar as
> handling CANCEL

Where did you put the handling of that kind of interrupt? Directly into
ProcessInterrupts()?

Probably. I don't remember it well, but it need hack code - it cannot be used from extension.

Pavel
 

Andres

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: to_json(NULL) should to return JSON null instead NULL
Next
From: Bruce Momjian
Date:
Subject: Re: Pg_upgrade remote copy