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-patches" <pgsql-patches(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Dbsize backend integration |
Date: | 2005-06-29 10:17:22 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E485077E@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
-----Original Message-----
From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)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 that though, 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2005-06-29 10:43:11 | Re: GiST concurrency commited |
Previous Message | Qingqing Zhou | 2005-06-29 10:09:34 | Re: GiST concurrency commited |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-06-29 11:45:44 | Re: Dbsize backend integration |
Previous Message | Abhijit Menon-Sen | 2005-06-29 09:47:31 | spi_query/spi_fetchrow for pl/perl |