Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key
Дата
Msg-id CABOikdOS9+iq+j-ZtKAmXwEtdgXXvJPQxED14nAU5j8F17wTXg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key  (Andres Freund <andres@anarazel.de>)
Ответы Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список 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 по дате отправления:

Предыдущее
От: Nikhil Sontakke
Дата:
Сообщение: Re: [HACKERS] logical decoding of two-phase transactions
Следующее
От: David Rowley
Дата:
Сообщение: Re: [HACKERS] Runtime Partition Pruning