Re: Dept of ugly hacks: eliminating padding space in system indexes - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Dept of ugly hacks: eliminating padding space in system indexes
Date
Msg-id 48610E6A.90709@commandprompt.com
Whole thread Raw
In response to Re: Dept of ugly hacks: eliminating padding space in system indexes  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus wrote:
> Shane Ambler wrote:
>> Mark Mielke wrote:
>>
>>> Not that I disagree with your change, but < 5 Mbytes in 4 Gbytes of 
>>> RAM for my main PostgreSQL system that I manage seems like a drop in 
>>> the bucket. Even if 40% of pg_class_relname and pg_proc_proname 
>>> indices was saved - we're talking about 154 Kbytes saved on both 
>>> those indices combined. Minor? Major? I bet I wouldn't notice unless 
>>> my database requirements used up all RAM, and even then I'm 
>>> suspecting it wouldn't matter except for border line cases (like all 
>>> pages required for everything else happened to equal 4 Gbytes near 
>>> exactly).
>>
>> Guess the mileage will vary depending on the complexity of the db 
>> structure. Shorter names will also benefit more than longer ones.
> 
> There are PostgreSQL users out there with more than 100,000 tables per 
> server instance.  This will make more of a difference to them.

More than I think people realize.

Joshua D. Drake

> 
> --Josh
> 
> 



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Dept of ugly hacks: eliminating padding space in system indexes
Next
From: "Joshua D. Drake"
Date:
Subject: Re: [PATCHES] Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout