Re: ToDo List Item - System Table Index Clustering

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: saiken(at)quietlycompetent(dot)com, Simone Aiken <saiken(at)ulfheim(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ToDo List Item - System Table Index Clustering
Date: 2011-01-19 20:10:39
Message-ID: 25733.1295467839@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jan 19, 2011 at 2:26 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Which brings up another point though. I have a personal TODO item to
>> make the comments for operator support functions more consistent:
>> http://archives.postgresql.org/message-id/21407.1287157253@sss.pgh.pa.us
>> Should we consider removing those comments altogether, instead?

> I could go either way on that. Most of those comments are pretty
> short, aren't they? How much storage are they really costing us?

Well, on my machine pg_description is about 210K (per database) as of
HEAD. 90% of its contents are pg_proc entries, though I have no good
fix on how much of that is for internal-use-only functions. A very
rough estimate from counting pg_proc and pg_operator entries suggests
that the answer might be "about a third". So if we do what was said in
the above-cited thread, ie move existing comments to pg_operator and
add boilerplate ones to pg_proc, we probably would pay <100K for it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-01-19 20:17:22 Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql
Previous Message Dimitri Fontaine 2011-01-19 20:00:31 Re: Extending opfamilies for GIN indexes