Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VOqdO-0000Dp-Jo for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Sep 2013 15:04:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VOqdO-0006Ah-3q for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Sep 2013 15:04:10 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VOqdM-0006AI-OO for pgsql-hackers@postgresql.org; Wed, 25 Sep 2013 15:04:08 +0000 Received: from mail-ea0-x229.google.com ([2a00:1450:4013:c01::229]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VOqdJ-0000a1-EZ; Wed, 25 Sep 2013 15:04:07 +0000 Received: by mail-ea0-f169.google.com with SMTP id k11so3309054eaj.28 for ; Wed, 25 Sep 2013 08:04:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=BYDvm8mcco1PshPq/reU8Fp/y32gAl+bCdnQhTX26hI=; b=qujBsl8a01Msoqc0x/I3Tjls1qMvNb93CcrjmEsdZGGig9VTR0HKEdAEUjbPQEis/c tfEEllCDkNteSheXUlzMACgR5aGyDJVtNOQ2P1+pOPN1e5mdTxgN5W9kMaQAi9nwEhhT u6vfEynAp7HPKo8ruafAZi3Pdimt5qtKFvGCWovVqTkmhguXMQf1ggqoy2dggaUkYUKF 3roAhVWA6FMYTh2f8Asxln2dlPA6PIIuJu0Zh0SOYbLKKbHxXI/3QPt+WLsiC2oEATTH iM45tDRiYnHtSMFxL61HrZKM1dVH6RvWhl85OViWGMEHUWLnU+gsFQIRmJ7HQOwFRaLo WcxQ== X-Received: by 10.14.183.2 with SMTP id p2mr24096354eem.44.1380121443714; Wed, 25 Sep 2013 08:04:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.130.71 with HTTP; Wed, 25 Sep 2013 08:03:23 -0700 (PDT) In-Reply-To: <7DCFAE8265254605840917B35EEF09F1@maumau> References: <20130920.085853.1628917054830864151.t-ishii@sraoss.co.jp> <20130922.072952.1977066018971837040.t-ishii@sraoss.co.jp> <5240B212.8040307@gmx.net> <7DCFAE8265254605840917B35EEF09F1@maumau> From: Greg Stark Date: Wed, 25 Sep 2013 16:03:23 +0100 X-Google-Sender-Auth: 5rTtZF9z8dYW91685C2mm9EOLdk Message-ID: Subject: Re: UTF8 national character data type support WIP patch and list of open issues. To: MauMau Cc: Peter Eisentraut , Robert Haas , Tatsuo Ishii , Tom Lane , maksymb@fast.au.fujitsu.com, Heikki Linnakangas , PostgreSQL-development Content-Type: multipart/alternative; boundary=047d7b343dc466710604e7369082 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --047d7b343dc466710604e7369082 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 24, 2013 at 1:04 PM, MauMau 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 --047d7b343dc466710604e7369082 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Tue, Sep 24, 2013 at 1:04 PM, MauMau <maumau307@gmail.com> wrote:
Yes, so Tatsuo san suggested to restrict server encoding <-> NCHAR en= coding 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 equiv= alent to text then.


--
greg
--047d7b343dc466710604e7369082--