Re: Dbsize backend integration - Mailing list pgsql-patches

From Dave Page
Subject Re: Dbsize backend integration
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E485077E@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Dbsize backend integration  ("Dave Page" <dpage@vale-housing.co.uk>)
Responses Re: Dbsize backend integration  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches


-----Original Message-----
From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
Sent: Wed 6/29/2005 2:16 AM
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration

> OK, so you went with relation as heap/index/toast only, and table as the
> total of them.  I am not sure that makes sense because we usually equate
> relation with table, and an index isn't a relation, really.

Err, yes - posted that before I got your reply!

> Do we have to use pg_object_size?  Is there a better name?  Are
> indexes/toasts even objects?

Yeah, I think perhaps pg_object_size is better in some ways than pg_relation_size, however I stuck with relation
because(certainly in pgAdmin world) we tend to think of pretty much anything as an object. I could go either way on
thatthough, however Michael doesn't seem so keen. 

So, one for pg_object_size, one on the fench and one against :-). Anyone else got a preference?

Regards, Dave.

pgsql-patches by date:

Previous
From: Abhijit Menon-Sen
Date:
Subject: spi_query/spi_fetchrow for pl/perl
Next
From: Bruce Momjian
Date:
Subject: Re: Dbsize backend integration