From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Declarative partitioning |
Date: | 2015-08-21 05:52:08 |
Message-ID: | 55D6BC88.4010101@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-08-21 AM 06:27, David Fetter wrote:
>> By the last sentence, do you mean only UPDATEs to the partition key that
>> cause rows to jump partitions or simply any UPDATEs to the partition key?
>
> I don't know what Simon had in mind, but it seems to me that we have
> the following in descending order of convenience to users, and I
> presume, descending order of difficulty of implementation:
>
> 1. Updates propagate transparently, moving rows between partitions if needed.
>
> 2. Updates fail only if the change to a partition key would cause the
> row to have to move to another partition.
>
> 3. All updates to the partition key fail.
>
I was thinking I'd implement 2.
There was some discussion last year[1] about how 1 could be realized.
Thanks,
Amit
[1]
http://www.postgresql.org/message-id/20140829172216.GF10109@awork2.anarazel.de
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2015-08-21 06:20:11 | Re: Declarative partitioning |
Previous Message | Amit Langote | 2015-08-21 05:47:50 | Re: Declarative partitioning |