outerNode->hashkeys = NULL issue

Discussion:

(too old to reply)

bshang

2011-02-27 21:34:03 UTC

When I was testing my code, I found that in ExecHashJoin, my
outerNode->hashkeys is NULL, which was definitely wrong. I doubted that
it was due to some mistakes in step 2. How should I fix this issue? Any
ideas?

Thanks,
S

Ken Salem

2011-02-27 23:01:05 UTC

Permalink

Hash nodes are a bit peculiar in postgres, in that they do not
completely initialize themselves. Some initialization is
done by the parent hash join node.

Check how the parent is initializing the original hash node,
and make sure your new outer hash node is being initialized
similarly.

-KMS

Post by bshang
When I was testing my code, I found that in ExecHashJoin, my
outerNode->hashkeys is NULL, which was definitely wrong. I doubted that
it was due to some mistakes in step 2. How should I fix this issue? Any
ideas?
Thanks,
S

Greg Knox

2011-03-06 19:50:16 UTC

Permalink

We are encountering the same problem and we think we have the same
initializations for the second hash node that were there for the
original one. No matter what we change, we cannot get a hashkeys value
for outerNode that doesn't cause a seg fault. Does anyone have any idea
what could be causing this?

Thanks,
Greg

Post by Ken Salem
Hash nodes are a bit peculiar in postgres, in that they do not
completely initialize themselves. Some initialization is
done by the parent hash join node.
Check how the parent is initializing the original hash node,
and make sure your new outer hash node is being initialized
similarly.
-KMS