You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're having some trouble with very long running 'idle in transsaction' connections from Prisma Queue.
Would it be possible to finish the transaction after running the polling query? It's definately the polling query and it stays in the 'idle in transaction' state for hours, which sets off an alarm in RDS.
UPDATE""queue_jobs""SET""processedAt""= NOW(), ""attempts""=""attempts""+1WHERE id = (
SELECT id
FROM""queue_jobs""WHERE (""queue_jobs"".""queue""= $1)
AND (""queue_jobs"".""finishedAt"" IS NULL)
AND (""queue_jobs"".""runAt""< NOW())
AND (""queue_jobs"".""notBefore"" IS NULLOR""queue_jobs"".""notBefore""< NOW())
ORDER BY""queue_jobs"".""priority""ASC, ""queue_jobs"".""runAt""ASC
FOR UPDATE SKIP LOCKED
LIMIT1
)
RETURNING *;
The text was updated successfully, but these errors were encountered:
We're having some trouble with very long running 'idle in transsaction' connections from Prisma Queue.
Would it be possible to finish the transaction after running the polling query? It's definately the polling query and it stays in the 'idle in transaction' state for hours, which sets off an alarm in RDS.
The text was updated successfully, but these errors were encountered: