From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Marc Mamin <M(dot)Mamin(at)intershop(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Declarative partitioning |
Date: | 2015-08-19 08:03:12 |
Message-ID: | 55D43840.5030504@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-08-19 AM 02:57, Marc Mamin wrote:
>> 2. Creating a partition of a partitioned table
>>
>> CREATE TABLE table_name
>> PARTITION OF partitioned_table_name
>> FOR VALUES values_spec;
>>
>> Where values_spec is:
>>
>> listvalues: [IN] (val1, ...)
>>
>
> Would it make sense to allow one complementary partition to the listvalues?
>
> listvalues: [[NOT] IN] (val1, ...)
>
> I've thought a few times about moving data with some most common values to dedicated partitions
> and keeping the rest in a separate one...
>
Thanks, that's definitely something to consider.
I have been thinking of a sort of default list partition for the "rest" of
values. Would you rather declare that with something like the below than
having to enumerate all the values in a NOT IN list? Or the NOT IN way is
more intuitive/friendly?
CREATE TABLE _rest PARTITION OF table_name FOR VALUES [ IN ] DEFAULT
Of course, at most one such partition would be allowed.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2015-08-19 08:49:46 | Re: allowing wal_level change at run time |
Previous Message | Masahiko Sawada | 2015-08-19 07:56:48 | Re: Freeze avoidance of very large table. |