Re: On-demand running query plans using auto_explain and signals

2015-08-30 10:34 GMT+02:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:

>
>
> 2015-08-30 10:30 GMT+02:00 Shulgin, Oleksandr <
> oleksandr(dot)shulgin(at)zalando(dot)de>:
>
>> 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?
>>
> I sent it to mailing list year ago

http://www.postgresql.org/message-id/CAFj8pRAXcS9B8ABgiM-zauVgGqDhPZOaRz5YSp1_Nhv9HP8nKw@mail.gmail.com

Regards

Pavel

> I am not sure I am able to find it - I'll try. We didn't use it on
> production.
>
>
>> Thanks!
>> --
>> Alex
>>
>
>