| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Same expression more than once in partition key |
| Date: | 2017-06-23 18:47:06 |
| Message-ID: | 1c49fd18-538a-e5f3-b7a2-b787022a5369@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/23/17 09:54, Tom Lane wrote:
>> However, I can use same expression more than once in partition key.
>
> ... and so, I can't get excited about extending it to expressions.
> Where would you stop --- for example, are i and (i) equal? What
> about (i) and (case when true then i else j end)? In principle,
> the system could recognize both those identities, but it seems
> silly to expend code on it just for nagware purposes.
We also allow the same column more than once in an index. We probably
don't have to be more strict here.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-23 18:52:50 | Re: shift_sjis_2004 related autority files are remaining |
| Previous Message | Peter Eisentraut | 2017-06-23 18:37:27 | Re: pgjdbc logical replication client throwing exception |