Dave Page wrote:
-----Original Message-----
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
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).
[from memory] the relation_components function adds components in a
questionable way, e.g. counting on index on the toast table as index. To
me, that's internal implementation detail, and should be counted as
toast table size too.
Regards,
Andreas
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
