On Wed, Mar 23, 2016 at 5:49 AM, Aleksander Alekseev <a.aleks...@postgrespro.ru> wrote: > I still believe that optimizing 1% blindly without considering possible > side effects this optimization can bring (other data alignment, some > additional machine instructions - just to name a few) and having no > way to measure these side effects is a bad idea. But I also admit a > possibility that I can somehow be wrong on this. So I rewrote this > patch one again :'( the way you suggested (without that alignment > related hack I tried, it's just too ugly). I also attached original > hashhdr-rmh.patch just to have both patches in one message so it would > be easier to find both patches in this thread.
Thanks! I can't think of anything else to worry about with regards to that version, so I have committed it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers