MIME-Version: 1.0
In-Reply-To: 
 <CANxoLDeBGRmq_kUUNNySXimzJO2Ebj0aQBdjNM+0JvP3_Yr9Dw@mail.gmail.com>
References: 
 <CANxoLDcZND0pjXtrDKRip2xjddzjWiMgY2AMmrqqFE_Yu4+tHw@mail.gmail.com>
 <CA+OCxowUuaNRX9jHmEVFpqT7JCbjn6vaxw+JJ6yrvVp69FZscg@mail.gmail.com>
 <CAPG3WN5NY-Xsa_+6HUQ3NMU_n7jRgJ8L6rjHfyzSLSHS=zZC0Q@mail.gmail.com>
 <CA+OCxoy1v+mq2P4ZL2v7mmyHmjwQmL=v8RR8CSRra_SV96nJDQ@mail.gmail.com>
 <CANxoLDeBGRmq_kUUNNySXimzJO2Ebj0aQBdjNM+0JvP3_Yr9Dw@mail.gmail.com>
From: Robert Eckhardt <reckhardt@pivotal.io>
Date: Thu, 27 Apr 2017 10:18:02 -0400
Message-ID: 
 <CAAtBm9Ve2FX4_jY9tv11UqK2BhNoLn118aeT4y=TieSAovL+AA@mail.gmail.com>
Subject: Re: Declarative partitioning in pgAdmin4
To: Akshay Joshi <akshay.joshi@enterprisedb.com>
Cc: Dave Page <dpage@pgadmin.org>, Shirley Wang <swang@pivotal.io>,
	pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary=94eb2c190014f6ea98054e269f3e
Precedence: bulk
Sender: pgadmin-hackers-owner@postgresql.org

--94eb2c190014f6ea98054e269f3e
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 27, 2017 at 7:01 AM, Akshay Joshi <akshay.joshi@enterprisedb.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

--94eb2c190014f6ea98054e269f3e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Apr 27, 2017 at 7:01 AM, Akshay Joshi <span dir=3D"ltr">&lt;<a =
href=3D"mailto:akshay.joshi@enterprisedb.com" target=3D"_blank">akshay.josh=
i@enterprisedb.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"ltr">Hi Dave<div><br></div><div>As per discussion I have change=
d the logic of showing partitioned table in browser tree. Attached is the s=
creenshot.=C2=A0</div><div>Let me know your thoughts. =C2=A0=C2=A0</div></d=
iv></blockquote><div><br></div><div>Greenplum has had declarative partition=
ing for quite some time, I haven&#39;t spent much time diving into the Post=
gres implementation specifically, however, we have had some pain and I woul=
d suggest a little bit of thought behind this.=C2=A0</div><div><br></div><d=
iv>The issues we consistently face:</div><div><ul><li>The huge (often thous=
ands sometimes tens of thousands) number of partitions makes rendering all =
of the partitions painfully slow and frequently not useful.</li><li>When en=
d users are interested in looking at their partitions they frequently don&#=
39;t want all of them displayed mindlessly=C2=A0</li><ul><li>They are looki=
ng at a subset of partitions</li><li>Partitions are typically grouped aroun=
d their inheritance properties.=C2=A0</li></ul></ul><div>-- Rob</div></div>=
</div></div></div>

--94eb2c190014f6ea98054e269f3e--