Re: [pgadmin-hackers] Declarative partitioning in pgAdmin4

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.

Perhaps, though I doubt that number would be common in Postgres. The problem though, is that there are both stats and sub-objects (indexes and triggers for example) that are part of the child partitions, not the parent - and they may differ from partition to partition.

I don't see that we have any choice but to display them so users can work with them.

• 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. 

How might you propose grouping them (based on the way they work in Postgres)?