Andrew Dunstan writes:
> On 08/22/2012 11:08 PM, Tom Lane wrote:
>> Curiously, I do *not* see the bug on my Fedora 16 machine, running
>> perl-5.14.2-198.fc16.x86_64
> Possibly we need to look at the output of perl -V to see if there's a
> difference.
Mine sez
Summary of my perl5 (revision 5 v
On 08/22/2012 11:08 PM, Tom Lane wrote:
Alex Hunsaker writes:
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.
Curiously, I do *not* see the bug on my Fedora 16 machine, running
perl-5.14.2-198.fc16.x86_64
I wondered
Alex Hunsaker writes:
>> 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.
Curiously, I do *not* see the bug on my Fedora 16 machine, running
perl-5.14.2-198.fc16.x86_64
I wondered if Fedora is carrying a patch that fi
On Mon, Aug 20, 2012 at 10:14 AM, Alvaro Herrera
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 wrote:
> >
> > > After upgrading from 8.4 to 9.1, one of my plperl functions stopped
> > > working properly.
>
> I
On 2012-08-20 18:36, Tom Lane wrote:
Alvaro Herrera writes:
Excerpts from Alex Hunsaker's message of lun ago 20 12:03:11 -0400 2012:
Hrm seems to work for me. What version of perl is this?
$ perl -V
Summary of my perl5 (revision 5 version 16 subversion 0) configuration:
I can reproduce the fa
Alvaro Herrera writes:
> Excerpts from Alex Hunsaker's message of lun ago 20 12:03:11 -0400 2012:
>> Hrm seems to work for me. What version of perl is this?
>> $ perl -V
>> Summary of my perl5 (revision 5 version 16 subversion 0) configuration:
> I can reproduce the failure with 5.14.2
Smells li
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 wrote:
>
> > After upgrading from 8.4 to 9.1, one of my plperl functions stopped
> > working properly.
> >
> > For some reason, when matching a string using a regex, the $1 va
On Sun, Aug 19, 2012 at 2:26 PM, Joel Jacobson wrote:
> After upgrading from 8.4 to 9.1, one of my plperl functions stopped
> working properly.
>
> For some reason, when matching a string using a regex, the $1 variable
> cannot be returned directly using return_next() but must be
> set to a varia
After upgrading from 8.4 to 9.1, one of my plperl functions stopped working
properly.
For some reason, when matching a string using a regex, the $1 variable
cannot be returned directly using return_next() but must be
set to a variable first.
If returned directly, it appears to be cached in some st
