| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alex Hunsaker <badalex(at)gmail(dot)com>, Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding. |
| Date: | 2011-10-06 16:19:23 |
| Message-ID: | 7E85AF2F-7B0D-4BF9-A2CE-8532628E2B0A@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Oct 5, 2011, at 7:36 PM, Robert Haas wrote:
>> The open commitfest? Even if its an "important" bug fix that should be
>> backpatched?
>
> Considering that the issue appears to have been ignored from
> mid-February until early October, I don't see why it should now get to
> jump to the head of the queue. Other people may have different
> opinions, of course.
Proper encoding of text data to and from Perl is more important every day, as it's used for more and more uses beyond ASCII. I think it's important to backport such issues modulo behavioral changes.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-10-06 19:46:58 | pgsql: Ensure walsenders can be SIGTERMed while in non-walsender code |
| Previous Message | Robert Haas | 2011-10-06 16:13:14 | Re: [COMMITTERS] pgsql: Ensure that contrib/pgstattuple functions respond to cancel |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-06 16:23:40 | Re: [REVIEW] Patch for cursor calling with named parameters |
| Previous Message | Robert Haas | 2011-10-06 16:13:14 | Re: [COMMITTERS] pgsql: Ensure that contrib/pgstattuple functions respond to cancel |