Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key
Date
Msg-id CABOikdOS9+iq+j-ZtKAmXwEtdgXXvJPQxED14nAU5j8F17wTXg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key
List pgsql-hackers


On Thu, Apr 5, 2018 at 7:14 AM, Andres Freund <andres@anarazel.de> wrote:


I've attached a noticeably editorialized patch:



+           /*
+            * As long as we don't support an UPDATE of INSERT ON CONFLICT for
+            * a partitioned table we shouldn't reach to a case where tuple to
+            * be lock is moved to another partition due to concurrent update
+            * of the partition key.
+            */
+           Assert(!ItemPointerIndicatesMovedPartitions(&hufd.ctid));
+
 
This is no longer true; at least not entirely. We still don't support ON CONFLICT DO UPDATE to move a row to a different partition, but otherwise it works now. See 555ee77a9668e3f1b03307055b5027e13bf1a715.

Thanks,
Pavan

--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Nikhil Sontakke
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: David Rowley
Date:
Subject: Re: [HACKERS] Runtime Partition Pruning