Log Message:
-----------
Fix Portal parameters.
Firstly, the PLI allocated in the Query's execution context was not lasting long
enough, and secondly, it was referening the parameter tuple allocated in the
execution context as well.
Fix this by making PyPgPortal_Initialize construct the PLI in the Portal's
heap and by referencing the input object's HeapTuple. So, spin off the PLI
creation into it's own function and use it when necessary.
Modified Files:
--------------
be/include/pypg:
query.h (r1.7 -> r1.8)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/include/pypg/query.h.diff?r1=1.7&r2=1.8)
be/include/pypg/call:
portal.h (r1.6 -> r1.7)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/include/pypg/call/portal.h.diff?r1=1.6&r2=1.7)
be/src:
query.c (r1.15 -> r1.16)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/src/query.c.diff?r1=1.15&r2=1.16)
be/src/call:
portal.c (r1.10 -> r1.11)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/src/call/portal.c.diff?r1=1.10&r2=1.11)
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
