From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Michael Glaesemann" <grzm(at)myrealbox(dot)com> |
Cc: | "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Dbsize backend integration |
Date: | 2005-06-30 09:24:55 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E490E83C@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> -----Original Message-----
> From: Michael Glaesemann [mailto:grzm(at)myrealbox(dot)com]
> Sent: 30 June 2005 10:01
> To: Dave Page
> Cc: PostgreSQL-patches; PostgreSQL-development
> Subject: Re: [PATCHES] Dbsize backend integration
>
>
> I'm still unclear as to what exactly is trying to be captured by the
> names, so I'll just throw some out and see if they're intuitive to
> anyone.
Thanks Michael. We have 2 functions - 1 returns the on disk size of a
table or index without any additional parts such as indexes or toast
tables. The other function returns the total on disk size of a table and
all associated indexes and toast tables (and any indexes they might
have). The current names are pg_relation_size() for the first function,
and pg_table_size() for the second.
> pg_table_extensions_size()
> pg_table_support_size()
> pg_relation_extensions_size()
> pg_relation_support_size()
>
> pg_relation_extended_size()
Hmm, none of those really stand out - but thanks anyway. More are
welcome :-)
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-06-30 09:28:19 | Re: Dbsize backend integration |
Previous Message | Michael Glaesemann | 2005-06-30 09:00:42 | Re: Dbsize backend integration |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-06-30 09:28:19 | Re: Dbsize backend integration |
Previous Message | Michael Glaesemann | 2005-06-30 09:00:42 | Re: Dbsize backend integration |