Skip to content

Create/update trigger on module installation #245

Closed

Description

@sbidoul

The database trigger that emits the NOTIFY events is created/updated during job runner startup.

When the runner crashes and restart (e.g. when the database connection is lost temporarily) it attempts to drop/recreate the trigger. This requires an exclusive lock on the queue_job table and causes issues when this happens while other transactions are busy creating many jobs.

A solution is to move the trigger creation to module installation time in a post init hook.

Activity

  1. transferred this issue fromOCA/connectoron Jul 23, 2020
  2. guewen commented on Oct 1, 2020

    @guewen
    Member

    Fixed by #247, #248 in 12.0/13.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions