From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Dawid Kuroczko" <qnex42(at)gmail(dot)com> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] Dbsize backend integration |
Date: | 2005-07-01 07:23:25 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E490E875@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Dawid Kuroczko [mailto:qnex42(at)gmail(dot)com]
> Sent: 30 June 2005 22:21
> To: Dave Page
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] [PATCHES] Dbsize backend integration
>
> On 6/30/05, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> wrote:
> > > -----Original Message-----
> > > From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> > > Sent: 29 June 2005 12:46
> > > To: Dave Page
> > > Cc: PostgreSQL-patches; PostgreSQL-development
> > > Subject: Re: [PATCHES] Dbsize backend integration
> > >
> > > 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? :-)
>
> pg_diskspace_size()
> pg_diskusage_size()
> pg_media_used_size()
> pg_allocated_size()
> pg_diskspace_used()
Unfortunately I think those are too generic - we also have
pg_database_size() and pg_tablespace_size() for which these would work.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-07-01 07:29:23 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
Previous Message | Satoshi Nagayasu | 2005-07-01 07:15:50 | enable/disable trigger (Re: Fwd: [HACKERS] Open items) |