Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Tryton Tryton
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 792
    • Issues 792
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TrytonTryton
  • TrytonTryton
  • Issues
  • #11293
Closed
Open
Issue created Mar 02, 2022 by Nicolas Évrard@nicoe👾Owner

Allow to specify database statement timeout on RPC calls

It could happen that a using a function field searcher numerous time on the search bar will result in a huge query that can take up to some hours and more importantly eat up all the memory and CPU dedicated to the database.

Thankfully postgres has an option available on the sessions: statement_timeout that allows to limit the time spent on each statement of the session.

The review implements this on the RPC level and adds it on search, search_count and on the global search. I chose the delay somehow randomly.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking