Alex Hunsaker <badalex(at)gmail(dot)com> writes:
> Oh my... I dunno exactly what I was smoking last night, but its a good
> thing I didn't share :-). Uh so my test program was also completely
> wrong, Ill have to redo it all. I've narrowed it down to:
>         if ((type == SVt_PVGV || SvREADONLY(sv)))
>         {
>             if (type != SVt_PV &&
>                 type != SVt_NV)
>             {
>                 sv = newSVsv(sv);
>             }
>        }

Has anyone tried looking at the source code for SvPVutf8 to see exactly
what cases it fails on?  The fact that there's an explicit croak() call
makes me think it might not be terribly hard to tell.

			regards, tom lane

In response to

• Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix. at 2012-01-06 19:02:49 from Alex Hunsaker

Responses

• Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix. at 2012-01-13 02:28:22 from Alex Hunsaker

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2012-01-06 21:14:27
	Subject: Re: Progress on fast path sorting, btree index creation time
Previous:	From: Simon Riggs	Date: 2012-01-06 20:49:37
	Subject: Re: 16-bit page checksums for 9.2

pgsql-committers by date

Next:	From: Robert Haas	Date: 2012-01-07 03:42:42
	Subject: pgsql: Improve behavior of concurrent ALTER TABLE,and do some refactor
Previous:	From: Robert Haas	Date: 2012-01-06 19:33:15
	Subject: pgsql: Make the number of CLOG buffers adaptive,based on shared_buffer