| From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Joel Jacobson <joel(at)trustly(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unexpected plperl difference between 8.4 and 9.1 |
| Date: | 2012-08-23 02:48:09 |
| Message-ID: | CAFaPBrSD4fOJqHBiZfWd5+8gnovirpiDJHftrNvA_gX5w8tUvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 20, 2012 at 10:14 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com>wrote:
> Excerpts from Alex Hunsaker's message of lun ago 20 12:03:11 -0400 2012:
> > On Sun, Aug 19, 2012 at 2:26 PM, Joel Jacobson <joel(at)trustly(dot)com> wrote:
> >
> > > After upgrading from 8.4 to 9.1, one of my plperl functions stopped
> > > working properly.
>
> I can reproduce the failure with 5.14.2
>
>
Me too, however it works for me with 5.14.1, looking more like a strange
perl bug.
I've tried reproducing this in straight perl but I don't think I can
without using some C code, specifically the call to SvPVutf8 in sv2cstr()
seems to be the culprit. If I change that to SvPV() it seems to work. Im
wondering if there is some strange caching of utf8 strings going on that =~
m// is not clearing.
Ill keep digging and hopefully be able to narrow it down to a commit
between 5.14.1 and 5.14.2 so we can understand more whats going here.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-08-23 03:08:25 | Re: Unexpected plperl difference between 8.4 and 9.1 |
| Previous Message | Tatsuo Ishii | 2012-08-23 02:46:38 | Re: Is this an appropriate item? |