From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | 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-10-30 12:24:01 |
Message-ID: | CA+HiwqG7Ksf+9VFcO00q-8GwnmjL=646ZzC-61vGbQFJ9EjDEg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 30, 2018 at 8:04 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> út 30. 10. 2018 v 7:52 odesílatel Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> napsal:
>> The patch to add the pg_partition_tree() function was just committed:
>>
>> Add pg_partition_tree to display information about partitions
>> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d5eec4eefde70
>>
>> Could one of you please revise the patch to use that function to produce
>> the output of \dP+?
>
>
> here it is.
>
> It is based on Mathias's patch. Although we can use pg_partition_tree on PostgreSQL, we still should to support PostgreSQL 10, 11 where this function is not available
Ah, I forgot that psql will need to consider 10 and 11 servers too.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-10-30 12:27:42 | Re: Should pg 11 use a lot more memory building an spgist index? |
Previous Message | Tom Lane | 2018-10-30 12:17:14 | Re: Getting fancy errors when accessing information_schema on 10.5 |