Launchpad itself

SQL statements recorded in oops reports should have a tied explain analyze output for them.

Bug #291579 reported by Diogo Matsubara
This bug report is a duplicate of:  Bug #604509: Log query plan for timeout oopses. Edit Remove
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

jml suggested that we could tie the output of a explain analyze to the queries recorded in OOPS reports.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Once this is done oops-tools need to be updated, filed as bug 291580

Revision history for this message
Stuart Bishop (stub) wrote : Re: [Bug 291579] [NEW] SQL statements recorded in oops reports should have a tied explain analyze output for them.

On Fri, Oct 31, 2008 at 8:33 PM, Diogo Matsubara
<email address hidden> wrote:
> Public bug reported:
>
> jml suggested that we could tie the output of a explain analyze to the
> queries recorded in OOPS reports.

I think this should be done in post production - not when generating
the OOPS - as it is too heavyweight a process to perform in an error
handler.

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/

Curtis Hovey (sinzui)
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

I feel we should not automatically run "explain analyze" ever, for even more important reasons than the speed. But see bug 604509.

Revision history for this message
Gary Poster (gary) wrote :

I decided to treat this as a duplicate rather than as a won't fix. Either would have been fine with me. I think "explain" in bug 604509 captures the intent of this idea.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.