| From: | Shirley Wang <swang(at)pivotal(dot)io> |
|---|---|
| To: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Declarative partitioning in pgAdmin4 |
| Date: | 2017-05-23 14:09:37 |
| Message-ID: | CAPG3WN6sKefWWYfg9A5=f-QOO9HAsg7krsuQ6FZwvojEuvSjCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
It's less about implementing what's easy, and more about implementing what
we know for sure will provide user value.
Given that in the expression you used, the variables 'a' and 'b' have
undefined values, there's still a chance that we're missing a large chunk
of context for successful implementation.
Could you explain what 'a' and 'b' represent?
Where would users find values for 'a' and 'b'? (are they columns?)
What is the use case for partitioning by (a+b)/2?
How frequently will people partition this way?
It's possible to design for the range and list partitions and know we can
achieve success because we understand how users would go through this
workflow. Not sure about expressions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Eckhardt | 2017-05-23 14:39:00 | Re: Declarative partitioning in pgAdmin4 |
| Previous Message | Akshay Joshi | 2017-05-23 05:47:00 | Re: Declarative partitioning in pgAdmin4 |