[midPoint] Postgresql errors. Normal?

[Chris Woods]

Hi all,
just wondering if anyone else has come across these error messages in their postgres logs:



2021-05-20 13:39:10.901 UTC [1537] ERROR:  could not serialize access due to concurrent update



2021-05-20 13:39:10.901 UTC [1537] STATEMENT:  update m_object set createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20



2021-05-20 13:40:19.775 UTC [1605] ERROR:  could not serialize access due to concurrent update



2021-05-20 13:40:19.775 UTC [1605] STATEMENT:  update m_object set createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20



2021-05-20 13:41:26.803 UTC [1673] ERROR:  could not serialize access due to concurrent update



2021-05-20 13:41:26.803 UTC [1673] STATEMENT:  update m_object set createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20



2021-05-20 13:41:26.870 UTC [1676] ERROR:  could not serialize access due to concurrent update



2021-05-20 13:41:26.870 UTC [1676] STATEMENT:  update m_object set createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20



2021-05-20 13:41:26.928 UTC [1676] ERROR:  could not serialize access due to concurrent update



2021-05-20 13:41:26.928 UTC [1676] STATEMENT:  update m_object set createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20

and whether they should be of concern or not :)

Thanks in advance,
Chris.

CHRIS WOODS
Identity Management
Information and Business Technology

Rohde & Schwarz GmbH & Co. KG
Mühldofstraße 15| 81671 München
Telefon: +49 89 4129 15735
Internet: https://www.rohde-schwarz.com<https://www.rohde-schwarz.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20210520/558c8720/attachment-0001.htm>