ERROR: could not serialize access due to concurrent update
418 views
Skip to first unread message
Geordie
unread,
May 2, 2017, 5:55:07 PM5/2/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to tryton
Hi
Postgresql keeps spitting these errors. Is it something I should be concerned about?
May 2 17:04:04 jtryton42 postgres[8923]: [3-1] ERROR: could not serialize access due to concurrent update May 2 17:04:04 jtryton42 postgres[8923]: [3-2] STATEMENT: UPDATE "ir_session" SET "write_uid" = 0, "write_date" = CURRENT_TIMESTAMP WHERE (("ir_session"."id" IN (1) )) May 2 17:04:04 jtryton42 postgres[8942]: [3-1] ERROR: could not serialize access due to concurrent update May 2 17:04:04 jtryton42 postgres[8942]: [3-2] STATEMENT: UPDATE "ir_session" SET "write_uid" = 0, "write_date" = CURRENT_TIMESTAMP WHERE (("ir_session"."id" IN (1) )) May 2 17:04:04 jtryton42 postgres[8931]: [3-1] ERROR: could not serialize access due to concurrent update May 2 17:04:04 jtryton42 postgres[8931]: [3-2] STATEMENT: UPDATE "ir_session" SET "write_uid" = 0, "write_date" = CURRENT_TIMESTAMP WHERE (("ir_session"."id" IN (1) )) ~ Thanks Geordie
Cédric Krier
unread,
May 3, 2017, 4:15:09 AM5/3/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to tryton
On 2017-05-02 14:11, Geordie wrote:
> Hi
>
> Postgresql keeps spitting these errors. Is it something I should be
> concerned about?