Re: hash_create API changes (was Re: speedup tidbitmap patch: hash BlockNumber) - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: hash_create API changes (was Re: speedup tidbitmap patch: hash BlockNumber)
Date
Msg-id 549A5F21.6020402@BlueTreble.com
Whole thread Raw
In response to Re: hash_create API changes (was Re: speedup tidbitmap patch: hash BlockNumber)  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 12/24/14, 12:27 AM, Jim Nasby wrote:
> There were several select-only runs on both to warm shared_buffers (set to 512MB for this test, and fsync is off).

BTW, presumably this ~380M database isn't big enough to show any problems with hash collisions, and I'm guessing you'd
needway more memory than what I have on this laptop. Might be worth looking into that on a machine with a serious
amountof memory.
 
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: hash_create API changes (was Re: speedup tidbitmap patch: hash BlockNumber)
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: alter user set local_preload_libraries.