| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperl fails with perl 5.28 |
| Date: | 2018-05-23 21:10:07 |
| Message-ID: | 10366.1527109807@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christoph Berg <myon(at)debian(dot)org> writes:
> Re: Tom Lane 2018-05-23 <23260(dot)1527026547(at)sss(dot)pgh(dot)pa(dot)us>
>> but TBH I think someone oughta file a bug report first.
> https://rt.perl.org/Public/Bug/Display.html?id=133220
Thanks. Looking at this again, it seems like the core of the problem
is that S_run_body's fell-off-the-end behavior is equivalent to an
explicit "exit(0)". Perhaps it should not be. I can see the point of
treating "exit(0)" as an unusual quasi-error case, but fell-off-the-end
probably shouldn't be.
However, then somebody would have to look around and see if there are
any other uses of my_exit(0) that need to be rethought ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2018-05-23 21:11:10 | Re: Time to put context diffs in the grave |
| Previous Message | Tom Lane | 2018-05-23 21:01:58 | Re: Time to put context diffs in the grave |