| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Same expression more than once in partition key |
| Date: | 2017-06-26 04:17:56 |
| Message-ID: | 8ef502b3-2428-cf85-0cf8-99807cde2ae7@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/06/24 5:04, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> We also allow the same column more than once in an index. We probably
>> don't have to be more strict here.
>
> There actually are valid uses for the same column more than once in
> an index, eg if you use a different operator class for each instance.
> I find it hard to envision a similar use-case in partitioning though.
So, does this mean we don't need to apply Nagata-san's patch for now?
As far as the partitioning internals are concerned, I see no harm in
allowing a column to appear more than once in the partition key. OTOH, I
too don't see a partitioning use-case which would require it.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2017-06-26 04:26:28 | Re: gen_random_uuid security not explicit in documentation |
| Previous Message | Masahiko Sawada | 2017-06-26 04:00:30 | Re: Setting pd_lower in GIN metapage |