使用批量更新时PostgreSQL共享锁定错误

如何解决使用批量更新时PostgreSQL共享锁定错误

我正在使用连接到我们的Salesforce CRM的Mulesoft API，运行选择查询，并检索将插入到我的Postgres DB中的记录的集合。该API会收集这些记录，将它们分成批次（当前设置为50条记录），然后运行带有insert的{​​{1}}并将其转换为upsert语句。

on conflict do update插入内容如下：

bulk mode

我在其中进行插入/更新的表的架构：

INSERT INTO ${heroku.postgresSql.schema}."crosswalk_contacts" ("contact_id","guid","source_org_id") VALUES (#[payload.contactId],#[payload.guid],#[payload.sourceOrgId]) ON CONFLICT ON CONSTRAINT "crosswalk_contacts_pkey" 
DO UPDATE SET guid = #[payload.guid] where ("crosswalk_contacts".guid,"crosswalk_contacts".source_org_id) is distinct from (excluded.guid,excluded.source_org_id);

最后，这是某些日志中出现的错误：

CREATE TABLE dev.crosswalk_contacts (
    guid character varying,contact_id character(18),source_org_id character varying(18),last_modified_date timestamp without time zone DEFAULT CURRENT_TIMESTAMP,CONSTRAINT crosswalk_contacts_pkey PRIMARY KEY (contact_id,source_org_id)
);

-- Indices -------------------------------------------------------

CREATE UNIQUE INDEX crosswalk_contacts_pkey ON dev.crosswalk_contacts(contact_id bpchar_ops,source_org_id text_ops);
CREATE INDEX index_guid ON dev.crosswalk_contacts((lower(guid::text)) text_ops);

在这些批量更新期间，似乎有时在现有会话/事务中已经写入某些内容，导致此共享锁定发生。

我很难弄清楚它是由于负载（批量模式upsert中有50个upserts）还是由于我如何设置约束而需要等待直到之前的插入出现以检查它的原因。约束完整性。

我该如何解决这个问题？如果是时间安排，我会假设增加Message : Batch entry 36 INSERT INTO public."crosswalk_contacts" ("contact_id","source_org_id") VALUES ('0030W00003SoN69QAF','205211BA-CFF6-479B-8B43-34CB90DCE11D','00Dd0000000hLocEAE') ON CONFLICT ON CONSTRAINT "crosswalk_contacts_pkey" DO UPDATE SET guid = '205211BA-CFF6-479B-8B43-34CB90DCE11D' where ("crosswalk_contacts".guid,excluded.source_org_id) was aborted: ERROR: deadlock detected Detail: Process 23261 waits for ShareLock on transaction 258009; blocked by process 23260. Process 23260 waits for ShareLock on transaction 258008; blocked by process 23261. Hint: See server log for query details. Where: while locking tuple (6001,1) in relation "crosswalk_contacts" Call getNextException to see other errors in the batch. (java.sql.BatchUpdateException). Element : /businesslogicBatch_Enterprise/process-records/0/0/0/upsertSub_Flow/subprocessors/1 @ asu-sf-mdm-xwalk:null:null -------------------------------------------------------------------------------- Exception stack is: Batch entry 36 INSERT INTO public."crosswalk_contacts" ("contact_id",1) in relation "crosswalk_contacts" Call getNextException to see other errors in the batch. (java.sql.BatchUpdateException). (org.mule.api.MessagingException) ，但是如果是DDL问题，我不太确定从哪里开始。

有想法吗？