From: | Robert Eckhardt <reckhardt(at)pivotal(dot)io> |
---|---|
To: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Shirley Wang <swang(at)pivotal(dot)io>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Declarative partitioning in pgAdmin4 |
Date: | 2017-04-27 14:18:02 |
Message-ID: | CAAtBm9Ve2FX4_jY9tv11UqK2BhNoLn118aeT4y=TieSAovL+AA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Apr 27, 2017 at 7:01 AM, Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com
> wrote:
> Hi Dave
>
> As per discussion I have changed the logic of showing partitioned table in
> browser tree. Attached is the screenshot.
> Let me know your thoughts.
>
Greenplum has had declarative partitioning for quite some time, I haven't
spent much time diving into the Postgres implementation specifically,
however, we have had some pain and I would suggest a little bit of thought
behind this.
The issues we consistently face:
- The huge (often thousands sometimes tens of thousands) number of
partitions makes rendering all of the partitions painfully slow and
frequently not useful.
- When end users are interested in looking at their partitions they
frequently don't want all of them displayed mindlessly
- They are looking at a subset of partitions
- Partitions are typically grouped around their inheritance
properties.
-- Rob
From | Date | Subject | |
---|---|---|---|
Next Message | Joao Pedro De Almeida Pereira | 2017-04-27 14:37:03 | Re: [patch] Dependents and Dependencies in GreenPlum |
Previous Message | Sarah McAlear | 2017-04-27 14:08:37 | Re: [pgAdmin4][Patch]: Fixed RM #2315 : Sorting by size is broken |