| From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Greg Stark <stark(at)mit(dot)edu>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: On-demand running query plans using auto_explain and signals |
| Date: | 2015-08-30 08:30:51 |
| Message-ID: | CACACo5QRi4AOUyZR_V3WewB3ucNNxwTisRm2R13soYNvfw4xZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Aug 29, 2015 7:31 PM, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
>
> 2015-08-29 18:36 GMT+02:00 Andres Freund <andres(at)anarazel(dot)de>:
>>
>> On 2015-08-29 18:27:59 +0200, Pavel Stehule wrote:
>> > 2015-08-29 18:25 GMT+02:00 Shulgin, Oleksandr <
oleksandr(dot)shulgin(at)zalando(dot)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.
Do you still have the code somewhere around? Did it see production use?
Thanks!
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2015-08-30 08:34:48 | Re: On-demand running query plans using auto_explain and signals |
| Previous Message | Pavel Stehule | 2015-08-30 05:34:29 | Re: to_json(NULL) should to return JSON null instead NULL |