From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: pg_(total_)relation_size and partitioned tables
Date: Tue, 2 Jan 2018 11:02:26 -0300
Message-ID: <20180102140226.qen2d4tskjueryno@alvherre.pgsql> (raw)
In-Reply-To: <93bef1b2-2ed0-c257-158e-efdf5b0ff9dd@2ndquadrant.com>
Peter Eisentraut wrote:
> But what are the uses for dealing with partial partition hierarchies?
> How easy do we need to make that?
If you have multilevel partitioning, say partitions per year per site.
What is the volume of 2017 compared to 2016, on each site? I don't
think it needs to be super easy, but it should be reasonable.
I think pg_partition_parent() should be a simple function doing one
catalog lookup (already implemented as get_partition_parent(),
but needs a "missing_ok" case), and pg_partition_root() an iterative
version of that.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, peter.eisentraut@2ndquadrant.com, david.rowley@2ndquadrant.com, Langote_Amit_f8@lab.ntt.co.jp, michael.paquier@gmail.com, robertmhaas@gmail.com
Subject: Re: pg_(total_)relation_size and partitioned tables
In-Reply-To: <20180102140226.qen2d4tskjueryno@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox