|From:||Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>|
|To:||Michael Paquier <michael(at)paquier(dot)xyz>|
|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|
|Views:||Raw Message | Whole Thread | Download mbox|
čt 29. 11. 2018 v 7:58 odesílatel Michael Paquier <michael(at)paquier(dot)xyz>
> On Thu, Nov 22, 2018 at 03:47:11PM +0100, Pavel Stehule wrote:
> > I have not feel well when I see in one report numbers 40 and 16, I see
> > more comfortable when I see 24 and 16, but for this I need a different
> > perspective
> > What do you think about it?
> Maybe, my thought is that this would be a separate patch, and that we
> had better keep it simple for now because that's complicated enough :)
any time, the behave should be consistent.
I agree, so there can be another patch, that reports more about partitioned
table for \d+
> So I would rather have a wrapper on top of pg_partition_tree which is
> useful for the user with matching patterns, which shows roughly:
> - the size of the whole partition tree from the root.
> - its direct parent if any. Potentially in the verbose output. This
> depends on how much users have multi-level partitions. My bet would be
> not that much, but more input from others is welcome.
> - perhaps its level in the hierarchy, if integrated most likely as part
> of the verbose output.
> Then with the set of commands, have a mapping close to how \d treats
> indexes and relations:
> - \dp shows information about partitioned tables or indexes, if no pattern
> is defined tables show up. If a partitioned index pattern shows up,
> then index information is displayed.
- \dpi and \dpt for respectively partitioned indexes and tables.
|Next Message||Alvaro Herrera||2018-11-30 19:12:16||Re: partitioned tables referenced by FKs|
|Previous Message||Peter Eisentraut||2018-11-30 18:54:53||Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query|