From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Same expression more than once in partition key |
Date: | 2017-06-27 13:32:19 |
Message-ID: | CA+TgmoZ34d_m5j8LSa5yfHfUDHtqW4uPX93r3EF9rm_vUj5i1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 23, 2017 at 4:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.
Maybe you already realize this, but partitioning, like index creation,
allows an opclass to be specified:
rhaas=# create table foo (a text, b text) partition by range (a
text_ops, b text_pattern_ops);
CREATE TABLE
I don't really see anybody wanting to do that, but I don't really see
anyone wanting to do with an index either.
My inclination is to reject this patch as not solving any actual problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | sanyam jain | 2017-06-27 13:51:37 | Re: pgjdbc logical replication client throwing exception |
Previous Message | Amit Kapila | 2017-06-27 13:19:50 | Re: Pluggable storage |