Andrew Dunstan <[EMAIL PROTECTED]> writes:
>>> Actually, my take on your analysis is that there should be a way to get
>>> at "use warnings" (I assume that's disallowed in trusted plperl).
>>
>> Yes, we can't allow "use" in trusted code. But we could turn it on in
>> plperl.c, just as we can turn on strict mode, and HEAD already has the
>> infrastructure for logging lexical warnings - that's a new feature. I
>> will investigate turning the switch.
> I spoke a bit rashly here. The only way I have been able to make it work
> so far in the Safe container is via the global -w flag - everything else
> I tried failed, although it worked just fine for untrusted code. I don't
> have lots of time to spend working out why.
I think we'd best put this on the TODO list for 8.2. It's awfully late
in the cycle to be rushing through half-thought-out features ...
regards, tom lane
---------------------------(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
