| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, mathias(at)brossard(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ToDo: show size of partitioned table |
| Date: | 2018-11-22 14:29:11 |
| Message-ID: | 20181122142911.GA12620@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 22, 2018 at 12:42:14PM +0100, Pavel Stehule wrote:
> Here my position is strong. \dP for me doesn't mean "tables or
> indexes" - it means "partition tables with total relation size". I
> don't see any sense to show tables and indexes in one report.
Please let me disagree on that point. \dP, \dPt and \dPi are commands
able to show information about respectively partitioned relations,
partitioned tables and partitioned indexes, which is not something only
related to the size of those partitions. Showing only the level of a
relation in its hierarchy may be useful, but that's confusing for the
user without knowing its direct parent or its top-most parent. For
multiple levels, the direct parent without the number in the hierarchy
seems enough to me. I may be of course wrong in designing those
concepts.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-11-22 14:47:11 | Re: ToDo: show size of partitioned table |
| Previous Message | Amit Kapila | 2018-11-22 14:21:15 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |