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

From Tom Lane
Subject Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key
Date
Msg-id 11930.1520522979@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> ... I suppose we could still decide that if we
> can't have that, we don't want update tuple routing at all, but I
> think that's an overreaction.

Between this thread and
<CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn+tQ7=Bcgjc8quqKsDViKQ@mail.gmail.com>
I am getting the distinct impression that that feature wasn't ready
to be committed.  I think that reverting it for v11 is definitely
an option that needs to be kept on the table.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: unique indexes on partitioned tables
Next
From: Prabhat Sahu
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)