Adminer version: 5.2.2-dev
Driver: PostgreSQL
Database version: 17

By accident, I have found out that MySQL has better support for Partitioning than PostgreSQL; that's something I can't tolerate! :)

I'm willing to create a PR, but there are some design decisions that must be addressed

1. How to list partitions in a list of tables?
   
   a) Should the partitions be listed at all? I think so..
   b) Should it be somehow distinguished? I think that giving it some prefix "P: TableName" for example will be great. There should also be a tooltip on the top of the "P:" which will show the name of the parent table
   In detail of a given table, we can be probably more verbose so using something like a breadcrumb
   Parent Table -> Current Table with a link to a parent might be handy

2. I would propose splitting the partitioning support to two levels... "partitioning_view" | "partitioning_edit"
   Partitioning is quite a complex feature, and TBH, I don't think that edit support is really necessary. I would aim (at least at the beginning) to only show the necessary information. At the table detail page (list of partitions), but without the possibility to edit it. I guess it would be more complicated and the benefit of it will be negligible.

Ideas / Opinions?