Hi,
   I had a chance to go through the Hash join code of Postgresql and had the
following thoughts.

- Currently postgres takes the heaptuple from the slot and creates and
minimal_tuple and copies it into the temp file.

I think the creation of minimal_tuple in the middle is a overhead which can
be avoided by creating a mem-map and directly creating the minimal_tuple in
the mem-map. Since Hash join is used mainly to join huge tables, this might
benefit those warehouse customers of postgres.

Am i missing something???

Thanks,
Gokul.

Reply via email to