Re: [HACKERS] UPDATE of partition key - Mailing list pgsql-hackers

From Amit Khandekar
Subject Re: [HACKERS] UPDATE of partition key
Date
Msg-id CAJ3gD9c5Jh3oGcjULG4S1W=5S2SZOBHqrK8hcwMVHEkzyOXM=w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] UPDATE of partition key  (David Fetter <david@fetter.org>)
Responses Re: [HACKERS] UPDATE of partition key  (David Fetter <david@fetter.org>)
List pgsql-hackers
On 14 February 2017 at 22:24, David Fetter <david@fetter.org> wrote:
> On Mon, Feb 13, 2017 at 05:31:56PM +0530, Amit Khandekar wrote:
>> Currently, an update of a partition key of a partition is not
>> allowed, since it requires to move the row(s) into the applicable
>> partition.
>>
>> Attached is a WIP patch (update-partition-key.patch) that removes
>> this restriction. When an UPDATE causes the row of a partition to
>> violate its partition constraint, then a partition is searched in
>> that subtree that can accommodate this row, and if found, the row is
>> deleted from the old partition and inserted in the new partition. If
>> not found, an error is reported.
>
> This is great!
>
> Would it be really invasive to HINT something when the subtree is a
> proper subtree?

I am not quite sure I understood this question. Can you please explain
it a bit more ...



pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Re: [HACKERS] Parallel Append implementation
Next
From: "Ideriha, Takeshi"
Date:
Subject: Re: [HACKERS] GUC for cleanup indexes threshold.