Re: partition tree inspection functions
Amit Langote <langote_amit_f8@lab.ntt.co.jp>
From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Michael Paquier <michael@paquier.xyz>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>,
Jesper Pedersen <jesper.pedersen@redhat.com>,
Robert Haas <robertmhaas@gmail.com>,
Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-10-01T07:27:57Z
Lists: pgsql-hackers
On 2018/10/01 15:27, Michael Paquier wrote: > On Mon, Oct 01, 2018 at 03:16:32PM +0900, Amit Langote wrote: >> I wasn't able to respond to some of issues that Jesper brought up with the >> approach taken by the latest patch whereby there is no separate >> pg_partition_level function. He said that such a function would be useful >> to get the information about the individual leaf partitions, but I was no >> longer sure of providing such a function separately. > > Perhaps that could be debated separately as well? From what I can see > what's available would unlock the psql patch which would like to add > support for \dP, or show the size of partitions more easily. Yeah, maybe there is no reason to delay proceeding with pg_partition_children which provides a useful functionality. > I am also > not completely sure that I see the use-case for pg_partition_level or > even pg_partition_root_parent as usually in their schemas users append > rather similar relation names to the parent and the children. Or > perhaps not? We can continue discussing that once we're done dealing with pg_partition_children and then some other patches that are pending due to it such as Pavel's. Thanks, Amit
Commits
-
Add pg_partition_tree to display information about partitions
- d5eec4eefde7 12.0 landed