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

From Shulgin, Oleksandr
Subject Re: On-demand running query plans using auto_explain and signals
Date
Msg-id CACACo5QRi4AOUyZR_V3WewB3ucNNxwTisRm2R13soYNvfw4xZg@mail.gmail.com
Whole thread Raw
In response to Re: On-demand running query plans using auto_explain and signals  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: On-demand running query plans using auto_explain and signals  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
<p dir="ltr">On Aug 29, 2015 7:31 PM, "Pavel Stehule" <<a
href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>>wrote:<br /> ><br /> ><br /> ><br /> >
2015-08-2918:36 GMT+02:00 Andres Freund <<a href="mailto:andres@anarazel.de">andres@anarazel.de</a>>:<br />
>><br/> >> On 2015-08-29 18:27:59 +0200, Pavel Stehule wrote:<br /> >> > 2015-08-29 18:25
GMT+02:00Shulgin, Oleksandr <<a href="mailto:oleksandr.shulgin@zalando.de">oleksandr.shulgin@zalando.de</a>><br
/>>> > > Good point.  There's still hope to set a flag and process it later on.<br /> >> > >
Willhave to check if it's possible to stay in the scope of a loaded module<br /> >> > > though.<br />
>><br/> >> > I had a workable prototype - and It was implemented very similar as<br /> >> >
handlingCANCEL<br /> >><br /> >> Where did you put the handling of that kind of interrupt? Directly into<br
/>>> ProcessInterrupts()?<br /> ><br /> ><br /> > Probably. I don't remember it well, but it need hack
code- it cannot be used from extension.<p dir="ltr">Do you still have the code somewhere around? Did it see production
use?<pdir="ltr">Thanks!<br /> --<br /> Alex<br /> 

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: to_json(NULL) should to return JSON null instead NULL
Next
From: Pavel Stehule
Date:
Subject: Re: On-demand running query plans using auto_explain and signals