Re: Dbsize backend integration

From: Michael Glaesemann <grzm(at)myrealbox(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
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:00:42
Message-ID: 9ECCAF07-2773-4DB6-A117-E463F47FE541@myrealbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


On Jun 30, 2005, at 5:48 PM, Dave Page wrote:
>> -----Original Message-----
>> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
>> Sent: 29 June 2005 12:46

<snip />

>> I have a new idea --- pg_storage_size().
>>
>
> I'm not against that one, but I think Tom's point is vaild. I cannot
> think of anything better at the moment though (maybe
> pg_component_size,
> but that's equally random) :-(
>
> Anyone else? Please? Someone? Anyone? :-)

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.

pg_table_extensions_size()
pg_table_support_size()
pg_relation_extensions_size()
pg_relation_support_size()

pg_relation_extended_size()

My two yen... if that :)

Michael Glaesemann
grzm myrealbox com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2005-06-30 09:24:55 Re: Dbsize backend integration
Previous Message Dave Page 2005-06-30 08:48:11 Re: Dbsize backend integration

Browse pgsql-patches by date

  From Date Subject
Next Message Dave Page 2005-06-30 09:24:55 Re: Dbsize backend integration
Previous Message Dave Page 2005-06-30 08:48:11 Re: Dbsize backend integration