Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M236744=pgsql-hackers-arkari@postgresql.org>)
 id 1VfQh4-0002cK-SA
 for pgsql-hackers@arkaria.postgresql.org; Sun, 10 Nov 2013 08:48:31 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M236744=pgsql-hackers-arkari@postgresql.org>)
 id 1VfQh4-0000bP-Ak
 for pgsql-hackers@arkaria.postgresql.org; Sun, 10 Nov 2013 08:48:30 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>) id 1VfQh2-0000aL-GT
 for pgsql-hackers@postgresql.org; Sun, 10 Nov 2013 08:48:28 +0000
Received: from mail-pd0-x22b.google.com ([2607:f8b0:400e:c02::22b])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>)
 id 1VfQgv-0000LP-EC; Sun, 10 Nov 2013 08:48:27 +0000
Received: by mail-pd0-f171.google.com with SMTP id w10so3918359pde.2
 for <multiple recipients>; Sun, 10 Nov 2013 00:48:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:from:to:cc:references:in-reply-to:subject:date
 :mime-version:content-type:content-transfer-encoding;
 bh=g1MW/viLiAa2lpz+CojVqEPDncZS5iqjVKhPqzDHr4I=;
 b=tD6QyXN5tIveE6C4DFQlDyHQbnedQhfSNVTu0b0iAlCoAcIy4WfJVHNuVDsBPoC2Vx
 t+uXj4ernUT1sRz8geKCEgnfRhKIp3DANYS+m+bxwUmMIZPia9D+znIPnvcX0OpCtKDg
 tas8MuoFWEI8saFGZBuINI5AhGl9DqFLOyBBoyKHJy7EZZrWGWOGcFmErcIkC5Vi8XPo
 LLlnq0YVBHQitZGYRpjNEPMTEv4XniryKJ5cp9aqmKlOT3JDIzeagtLiUXRvmzhMow6t
 u6dvFVuAAcqe4PhAC9OJvWDugef40j3yXEa1pybNHoV4pNNHhlom8ZpQOPwXDLxqaXrh
 ctRQ==
X-Received: by 10.68.219.167 with SMTP id pp7mr24118927pbc.125.1384073299829;
 Sun, 10 Nov 2013 00:48:19 -0800 (PST)
Received: from maumau (p3063-ipbfp1101sizuokaden.shizuoka.ocn.ne.jp.
 [114.157.166.63])
 by mx.google.com with ESMTPSA id ja5sm23205804pbc.14.2013.11.10.00.48.16
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Sun, 10 Nov 2013 00:48:18 -0800 (PST)
Message-ID: <319421D1A92A44BEAFD8E76AC86FB7AA@maumau>
From: "MauMau" <maumau307@gmail.com>
To: "Albe Laurenz" <laurenz.albe@wien.gv.at>,
 "Robert Haas" <robertmhaas@gmail.com>, "Peter Eisentraut" <peter_e@gmx.net>
Cc: "Arulappan, Arul Shaji" <arul@fast.au.fujitsu.com>,
 "Greg Stark" <stark@mit.edu>, "Tatsuo Ishii" <ishii@postgresql.org>,
 "Tom Lane" <tgl@sss.pgh.pa.us>,
 "Boguk, Maksym" <Maksym.Boguk@au.fujitsu.com>,
 "Heikki Linnakangas" <hlinnakangas@vmware.com>,
 "PostgreSQL-development" <pgsql-hackers@postgresql.org>
References: 
 <CA+TgmobWv_96dSfSHv2ZJWSXAD=QTiBEKw-LT359sGArYe+AXQ@mail.gmail.com><20130920.085853.1628917054830864151.t-ishii@sraoss.co.jp><CA+TgmoZEy=pt2B5D+nuPAib7KvhNoBgRGYRWnkS4pyrqfcdYHQ@mail.gmail.com><20130922.072952.1977066018971837040.t-ishii@sraoss.co.jp><D0A2FE73E8354EDCBEE56EC79268CA4E@maumau><5240B212.8040307@gmx.net><7DCFAE8265254605840917B35EEF09F1@maumau><CAM-w4HMRCTyemtmKDJPHL72dXH1Gr6q5JrkCNnE63RXLn02Tjw@mail.gmail.com><7C2A735AFC3E4088A8F49B677855369C@maumau><022C711CCA8AF2459F370E936F2B9E8C0255E4BB@SYDExchTmp.au.fjanz.com><52796E11.8010501@gmx.net>
 <CA+TgmoYdsztyG4ML=N69rj2q2XTTjogE38aFtXJxrpyqS9WLjA@mail.gmail.com>,
 <673E261C589440E3B0D8FDF9A11B1181@maumau>
 <A737B7A37273E048B164557ADEF4A58B17C57F0B@ntex2010i.host.magwien.gv.at>
In-Reply-To: 
 <A737B7A37273E048B164557ADEF4A58B17C57F0B@ntex2010i.host.magwien.gv.at>
Subject: Re: UTF8 national character data type support WIP patch and list of
 open issues.
Date: Sun, 10 Nov 2013 17:48:21 +0900
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
 reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
X-Pg-Spam-Score: -1.3 (-)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

From: "Albe Laurenz" <laurenz.albe@wien.gv.at>
In a way, it is similar to using the "data type" serial.  The column will be
displayed as "integer", and the information that it was a serial can
only be inferred from the DEFAULT value.
It seems that this is working fine and does not cause many problems,
so I don't see why things should be different here.


Yes, I agree with you in that serial being a synonym is almost no problem. 
But that's because serial is not an SQL-standard data type but a type unique 
to PostgreSQL.

On the other hand, nchar is an established data type in the SQL standard.  I 
think most people will expect to get "nchar" as output from psql \d and 
pg_dump as they specified in DDL.  If they get "char" as output for "nchar" 
columns from pg_dump, wouldn't they get in trouble if they want to import 
schema/data from PostgreSQL to other database products?  The documentation 
for pg_dump says that pg_dump pays attention to easing migrating to other 
DBMSs.  I like this idea and want to respect this.

http://www.postgresql.org/docs/current/static/app-pgdump.html
--------------------------------------------------
Script files can be used to reconstruct the database even on other machines 
and other architectures; with some modifications, even on other SQL database 
products.
...
--use-set-session-authorization
Output SQL-standard SET SESSION AUTHORIZATION commands instead of ALTER 
OWNER commands to determine object ownership. This makes the dump more 
standards-compatible, ...
--------------------------------------------------


Regards
MauMau



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers