| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PG 8.1beta3 out soon |
| Date: | 2005-10-11 13:38:25 |
| Message-ID: | 13535.1129037905@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-10-11 13:39:45 | Re: NZ mirror |
| Previous Message | Andrew Dunstan | 2005-10-11 13:03:34 | Re: PG 8.1beta3 out soon |