Re: UTF8 national character data type support WIP patch and list of open issues.

From: Greg Stark <stark(at)mit(dot)edu>
To: MauMau <maumau307(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, maksymb(at)fast(dot)au(dot)fujitsu(dot)com, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: UTF8 national character data type support WIP patch and list of open issues.
Date: 2013-09-25 15:03:23
Message-ID: CAM-w4HMRCTyemtmKDJPHL72dXH1Gr6q5JrkCNnE63RXLn02Tjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 24, 2013 at 1:04 PM, MauMau <maumau307(at)gmail(dot)com> wrote:

> Yes, so Tatsuo san suggested to restrict server encoding <-> NCHAR
> encoding combination to those with lossless conversion.

If it's not lossy then what's the point? From the client's point of view
it'll be functionally equivalent to text then.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-09-25 15:08:04 Re: logical changeset generation v6
Previous Message Steve Singer 2013-09-25 15:01:44 Re: logical changeset generation v6