| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0) |
| Date: | 2010-02-25 18:05:03 |
| Message-ID: | 793249CF-DED6-440A-9771-C50554EE3CBB@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Feb 25, 2010, at 10:01 AM, Tim Bunce wrote:
>> That's two unacceptable alternatives, you need to find a third one.
>> I think most people will have no trouble settling on "do not update
>> to Safe 2.2x" if you don't offer a better solution than these.
>
> I believe the next version of Safe will revert to Safe 1.19 behaviour
> because the side effects of the change in 2.20 are too severe for it to
> be left enabled by default.
Which means losing sort $a <=> $b again, alas. Such was always the case in the past, so that might be an okay tradeoff to get recursive calls working again, but I certainly hope that Safe can be updated in the near future to give us both.
There seem to be no good answers here.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-02-25 18:32:31 | Re: to_timestamp error handling. |
| Previous Message | David E. Wheeler | 2010-02-25 18:04:44 | Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0) |