DBLoopTuner often cannot detect long running transactions

Bug #351363 reported by Stuart Bishop
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Stuart Bishop

Bug Description

If the DBLoopTuner is not connected to the database as a superuser, the long running transaction detection silently fails. This happens because the pg_stat_activity view just returns NULL for information it considers privileged, such as the xact_start we depend on.

A security definer stored procedure would work around this issue. The only column we might need to protect is the current_query.

Stuart Bishop (stub)
Changed in launchpad-foundations:
importance: Undecided → Medium
status: New → Triaged
Stuart Bishop (stub)
Changed in launchpad-foundations:
assignee: nobody → stub
status: Triaged → In Progress
Stuart Bishop (stub)
Changed in launchpad-foundations:
milestone: none → 2.2.4
Stuart Bishop (stub)
Changed in launchpad-foundations:
milestone: 2.2.4 → 2.2.5
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit

Fixed in db r8060.

Changed in launchpad-foundations:
status: In Progress → Fix Committed
Stuart Bishop (stub)
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.

Other bug subscribers