Joe Conway <[EMAIL PROTECTED]> writes:
> Actually, adding a "pfree(oneres);" to the end of that for loop plugs 
> the memory leak and allows me to see the error message:

Good catch.

> Takes a while to check all 16777216 possibilities though, so I'm still 
> not sure more isn't needed here.

I wonder why it's doing anything at all --- the check for supertypes
ought to trigger only for complex type (rowtype) arguments, and there
are none here.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to