Re: Declarative partitioning - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Declarative partitioning
Date
Msg-id CABOikdPX9RqV0x6UO9LxMaugmcwsx=ajbYeacfT3BROYnYGxXA@mail.gmail.com
Whole thread Raw
In response to Re: Declarative partitioning  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers


On Fri, Aug 21, 2015 at 11:22 AM, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
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.


+1. IMHO thats a good starting point. 

Thanks,
Pavan

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

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Declarative partitioning
Next
From: Simon Riggs
Date:
Subject: Re: Using quicksort for every external sort run