Re: ToDo: log plans of cancelled queries

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ToDo: log plans of cancelled queries
Date: 2013-01-11 16:24:11
Message-ID: CAFj8pRD+wtUY+bWmRMJo3b9PDoc0_MdjLsS0w2C04toTZLiYQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/1/11 Stephen Frost <sfrost(at)snowman(dot)net>:
> * Pavel Stehule (pavel(dot)stehule(at)gmail(dot)com) wrote:
>> 2013/1/11 Stephen Frost <sfrost(at)snowman(dot)net>:
>> > Why not an option to auto_explain (or whatever) to log an execution plan
>> > right before actually executing it? If that was something which could
>> > be set with a GUC or similar, you could just do that before running
>> > whatever queries you're interested in capturing the plans for.
>>
>> for our OLAP usage it is probably possible, but it can be slow for OLTP usage..
>
> If it was a GUC, you could turn it on/off at appropriate places in the
> OLTP scenario.

but still - if this is a auto_explain feature - then we need to return
execution to auto_explain after cancelled query - and it is probably
impossible now

Regards

Pavel

>
> Thanks,
>
> Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2013-01-11 16:28:01 Re: ToDo: log plans of cancelled queries
Previous Message Pavel Stehule 2013-01-11 16:20:39 Re: ToDo: log plans of cancelled queries