Re: ToDo: log plans of cancelled queries
От | Pavel Stehule |
---|---|
Тема | Re: ToDo: log plans of cancelled queries |
Дата | |
Msg-id | CAFj8pRBq-A6XUvqHHTdy46Ts6Gp9DAPDwYv6oVTYVh=kF0xSOw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ToDo: log plans of cancelled queries (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: ToDo: log plans of cancelled queries
|
Список | pgsql-hackers |
2013/1/11 Stephen Frost <sfrost@snowman.net>: > * Pavel Stehule (pavel.stehule@gmail.com) wrote: >> My propose is proposed for different dimensions and purpose - for >> example - we have a limit 20 minutes for almost all queries, and after >> this limit we killing queries. But we have to know little bit more >> about these bad queries - and we hope, so execution plan can give this >> additional info. We have same motivation like people who use >> auto_explain for slow query - but we can't to wait to query complete. > > 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.. Regards Pavel > > Thanks, > > Stephen
В списке pgsql-hackers по дате отправления: