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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>
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:34:48
Message-ID: CAFj8pRAZuB9ce2s8Q=xmiHftV_fOttx7G5mh4KU00PnvNv=nwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 am not sure I am able to find it - I'll try. We didn't use it on
production.

> Thanks!
> --
> Alex
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2015-08-30 10:29:45 datestyle=postgres broken with timezone=UTC+N
Previous Message Shulgin, Oleksandr 2015-08-30 08:30:51 Re: On-demand running query plans using auto_explain and signals