1. 03 Aug, 2021 1 commit
  2. 02 Aug, 2021 12 commits
  3. 30 Jul, 2021 2 commits
    • Bartek Wrona's avatar
      Merge branch 'mi_report_explain' into 'develop' · 4512a40f
      Bartek Wrona authored
      report explain analyze to log for given queries
      
      See merge request !529
      4512a40f
    • Marcin's avatar
      report explain analyze to log for given queries · 1dd32da6
      Marcin authored
      If some SQL query is suspected to will need be explained and analyzed in the future, then instead of
      call queries directly on Db instance call the same query on AutoExplainWrapper
      returned from the Db with method explain(). AutoExplainWrapper has the
      same query interface as the Db class has, so the call is identical in
      both cases.
      For example previously query executed without plan explanation:
      	db.query_row(sql)
      can be capable to explain with:
      	db.explain().query_row(sql)
      
      Because taking plan explanation requires SUPERUSER privileges and
      adds additional overhead for the queries, by default AutoExplainWrapper
      is not used, explain() function simply returns the Db class instance.
      To include plan explanation in the log hivemind has to be started
      with parameter --log_explain_queries=true and connected to the
      postgres db using role with SUPERUSER privileges.
      
      include information from vacuum analyze hive posts in the log
      1dd32da6
  4. 29 Jul, 2021 2 commits
  5. 27 Jul, 2021 1 commit
  6. 26 Jul, 2021 1 commit
  7. 23 Jul, 2021 2 commits
  8. 22 Jul, 2021 1 commit
  9. 21 Jul, 2021 5 commits
  10. 20 Jul, 2021 9 commits
  11. 19 Jul, 2021 4 commits