2013/1/11 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.com> writes: >> What do you thinking about this feature? > > The idea of expecting an add-on module to execute operations in an > already-failed transaction seems pretty dubious to me. I also think > it's not a great idea to add partial executions into a query's stats. > For instance, suppose query X has been done 3 times and took a minute > each time. The fourth time, the user cancels it after one second. > If we now report that the query's average execution time is 45 seconds > or so, that seems pretty misleading to me.
I don't propose logging query time for cancelled queries - although we have path that do it - but it is our specific issue. 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. Regards Pavel > > regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
