Launchpad itself

DBLoopTuner's listing of long-running transactions confuses

Bug #387694 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Jeroen T. Vermeulen
Launchpad itself 2.2.6

Bug Description

When the DBLoopTuner blocks to let long-running transactions finish, it lists those transactions' current_query, but only if it's an "idle" message. Otherwise it lists None, to avoid exposing potentially sensitive data in log files.

It'd be more helpful if it said something like "Busy" instead.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Fixed in devel 8655.

Changed in launchpad:
assignee: nobody → Jeroen T. Vermeulen (jtv)
importance: Undecided → Low
milestone: none → 2.2.6
status: New → Fix Committed
Diogo Matsubara (matsubara)
affects: launchpad → launchpad-foundations
Changed in launchpad-foundations:
milestone: 2.2.6 → none
milestone: none → 2.2.6
Revision history for this message
Stuart Bishop (stub) wrote :

We should expose the username, and also report autovacuum queries as they are not security sensitive at all. I'd replace other queries with <hidden> or similar.

Jeroen T. Vermeulen (jtv)
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
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.