| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | viy(at)mits(dot)lv |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, 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 22:21:07 |
| Message-ID: | 200506302221.j5UML7c02508@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
viy(at)mits(dot)lv wrote:
> > > 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? :-)
>
> Maybe pg_trait_size() or pg_property_size() will do?
I don't think so. I think trait and property suggests an aspect of the
object, so saying trait/property size is saying I am talking about an
aspect of the object, while for a heap, its size is really its size, it
isn't an aspect of its size.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-06-30 22:39:43 | 2PC transaction id |
| Previous Message | Tom Lane | 2005-06-30 22:18:49 | Re: Backend working directories and absolute file paths |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-06-30 22:39:43 | 2PC transaction id |
| Previous Message | Bruce Momjian | 2005-06-30 22:16:37 | Re: Dbsize backend integration |