Re: Patch for bug #12845 (GB18030 encoding)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Arjen Nienhuis <a(dot)g(dot)nienhuis(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for bug #12845 (GB18030 encoding)
Date: 2015-05-06 16:25:01
Message-ID: CA+TgmoZdi1qveeH-0uUbNJx5iFk+qgZOjHFetA2nR8rgmEhRRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 6, 2015 at 11:13 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
>> It's a behavior change, so I don't think we would consider a back-patch.
>
> Maybe not, but at the very least we should consider getting it fixed in
> 9.5 rather than waiting a full development cycle. Same as in
> https://www.postgresql.org/message-id/20150428131549.GA25925@momjian.us
> I'm not saying we MUST include it in 9.5, but we should at least
> consider it. If we simply stash it in the open CF we guarantee that it
> will linger there for a year.

Sure, if somebody has the time to put into it now, I'm fine with that.
I'm afraid it won't be me, though: even if I had the time, I don't
know enough about encodings.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-05-06 16:54:01 Re: Manipulating complex types as non-contiguous structures in-memory
Previous Message Andres Freund 2015-05-06 15:20:07 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0