From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DBSize backend integration |
Date: | 2005-06-24 20:14:06 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E490E71B@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: 24 June 2005 21:07
> To: Dave Page
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] DBSize backend integration
>
> > >
> > > So drop total_relation_size(),
> relation_size_components(), and what
> > > else?
> >
> > indexes_size()
>
> What is the logic for removing that? Because it is an
> aggregate of all
> indexes?
Yes, and is of limited use in my opinion. I can see a use for
pg_relation_size when used on an individual index, but the total of all
indexes on a relation seems of little real use to me (and is relatively
easily calculated if it really is required for a more specialised
purpose).
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Bob | 2005-06-24 20:19:32 | Re: PL/pgSQL Debugger Support |
Previous Message | Andrew Dunstan | 2005-06-24 20:12:14 | Re: DBSize backend integration |