Re: [HACKERS] Dbsize backend integration - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: [HACKERS] Dbsize backend integration
Date
Msg-id 200507022335.j62NZ3E28264@candle.pha.pa.us
Whole thread Raw
In response to Re: Dbsize backend integration  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: [HACKERS] Dbsize backend integration
Re: [HACKERS] Dbsize backend integration
List pgsql-patches
Andreas Pflug wrote:
> Dave Page wrote:
> >
> >
> >
> >>-----Original Message-----
> >>From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> >>Sent: 02 July 2005 21:30
> >>To: Bruce Momjian
> >>Cc: Dave Page; PostgreSQL-patches; PostgreSQL-development
> >>Subject: Re: [PATCHES] Dbsize backend integration
> >>
> >>
> >>Is a new version of this patch coming?
> >
> >
> > Yup, attached. Per our earlier conversation, pg_dbfile_size() now
> > returns the size of a table or index, and pg_relation_size() returns the
> > total size of a relation and all associated indexes and toast tables
> > etc.
>
> pg_relation_size's name is quite unfortunate, since the 8.0 contrib
> function does something different. And pg_dbfile_size sounds misleading,
> suggesting it takes a filename or relfilenode as parameter.

Hmm.  I don't see how we can call it pg_table_size because people think
of tables and indexes, while relation has a more inclusive suggestion.

As far as pg_dbfile_size, do you have any other idea for a name?  To me,
it returns the size of the 'db file' associated with the
heap/index/toast.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Problem with dblink regression test - FIXED
Next
From: Stephen Frost
Date:
Subject: Re: per user/database connections limit again