Re: BUG #15245: pg_stat_all_tables does not include partition master tables

From: Mahadevan Ramachandran <mahadevan(at)rapidloop(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15245: pg_stat_all_tables does not include partition master tables
Date: 2018-06-18 13:58:15
Message-ID: CADjCDK9v4LK+8HhtjFeF4D1q5W=OgCPwA6S2oP47nCVM4zafkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 18, 2018 at 3:51 PM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> about how to aggregate across partitions. We could leave that NULL for
> now, that is, if we decide to list partitioned tables in the
> pg_stat_all_tables output at all re OP's complaint.

"Complaint" is too strong a word :-)

I guess the real issue is that both options are a bit inconsistent. Not listing
a partitoned table in an "all tables" view does not seem any worse or better
than having it there with all columns as NULL. Should've thought about it
before I raised the bug :-)

Might I suggest a new system view that lists all (parent, child) associations,
which can then be joined with pg_stat_all_tables so users can roll up
child table stats into each parent using whatever aggregation functions
they'd like?

Thanks for your time.

-Mahadevan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mario Emmenlauer 2018-06-18 19:46:01 Re: BUG #15243: make check shows errors, i.e. fails to find initdb and others
Previous Message Michael Paquier 2018-06-18 12:49:43 Re: BUG #15245: pg_stat_all_tables does not include partition master tables