sometimes error will emit at start() because of deadlock

[timgit]

Ran into this recently so creating this for future reference. This hapens during start() since multiple promises run simultaneously to begin monitoring the job tables. connect() is not affected. The impact of this should be low, since the intervals of running each query in question are different and the likelihood of this specific collision is so low the only time I've seen this emit the error event is at start().

    "err": {
        "type": "Error",
        "message": "deadlock detected",
        "stack": "error: deadlock detected\n    at Connection.parseE (/opt/infocyte/api/node_modules/pg/lib/connection.js:604:11)\n    at Connection.parseMessage (/opt/infocyte/api/node_modules/pg/lib/connection.js:401:19)\n    at TLSSocket.<anonymous> (/opt/infocyte/api/node_modules/pg/lib/connection.js:121:22)\n    at TLSSocket.emit (events.js:210:5)\n    at TLSSocket.EventEmitter.emit (domain.js:476:20)\n    at addChunk (_stream_readable.js:308:12)\n    at readableAddChunk (_stream_readable.js:289:11)\n    at TLSSocket.Readable.push (_stream_readable.js:223:10)\n    at TLSWrap.onStreamRead (internal/stream_base_commons.js:182:23)",
        "name": "error",
        "length": 332,
        "severity": "ERROR",
        "code": "40P01",
        "detail": "Process 5611 waits for ShareLock on transaction 244217582; blocked by process 5612.\nProcess 5612 waits for ShareLock on transaction 244217534; blocked by process 5611.",
        "hint": "See server log for query details.",
        "where": "while deleting tuple (3269,8) in relation \"job\"",
        "file": "deadlock.c",
        "line": "1146",
        "routine": "DeadLockReport"
    },