From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dawid Kuroczko <qnex42(at)gmail(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Dbsize backend integration |
Date: | 2005-07-05 01:38:30 |
Message-ID: | 42C9E496.3020907@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
>>You are into the cycle we were in. We discussed pg_object size (too
>>vague) and pg_index_size (needs pg_toast_size too, and maybe toast
>>indexes; too many functions).
>
> Yeah, I read those discussions, and think you were better off then than you
> are now, which is why I went back to it somewhat.
To be honest, the amount of effort being expended on this naming
discussion far outweighs the benefits. Maybe it's time for a core
member to step in and just resolve it - one way or the other?
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-05 03:33:34 | Re: New warnings in plgsql/src/scan.l |
Previous Message | Robert Treat | 2005-07-05 01:34:17 | Re: [HACKERS] Dbsize backend integration |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2005-07-05 03:21:46 | Re: Autovacuum integration patch |
Previous Message | Robert Treat | 2005-07-05 01:34:17 | Re: [HACKERS] Dbsize backend integration |