Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bsapt-0004Fg-Of for pgsql-sql@arkaria.postgresql.org; Fri, 07 Oct 2016 19:29:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bsapt-0005tr-2F for pgsql-sql@arkaria.postgresql.org; Fri, 07 Oct 2016 19:29:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bsapr-0005sT-AV for pgsql-sql@postgresql.org; Fri, 07 Oct 2016 19:29:35 +0000 Received: from mout.kundenserver.de ([212.227.126.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84_2) (envelope-from ) id 1bsapn-0005kw-PT for pgsql-sql@postgresql.org; Fri, 07 Oct 2016 19:29:34 +0000 Received: from [192.168.178.26] ([84.165.205.46]) by mrelayeu.kundenserver.de (mreue002) with ESMTPSA (Nemesis) id 0M0Y5m-1b28s31dgE-00uqWV for ; Fri, 07 Oct 2016 21:29:29 +0200 Subject: Re: Large Objects References: <8d8248b8-8535-787b-5cb7-f081be778b70@purtz.de> To: postgres list From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= Message-ID: <95bef507-ed75-2ca9-7914-2a243d326ab3@purtz.de> Date: Fri, 7 Oct 2016 21:31:29 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:5OSU7Lp+y5x4sw1XDMo7pSywdM8e3Lufr2cb0Z2yUbON6BHfJ1Y fYi/mgmYuTAv2KKJfh8B+6JQJWLS8+ndnSu1Ee4aIWEQQIFJqR8MR0/A+DWjiVhwF8R09tn YJUGfJoh2GdDKdWF2NOtUUP2ZhQM5xyoo5WD//rCMpoTHmBsdRLXMARiXkL9ckFV0B3ey3p cBmAnpWY7BTn23dQkiDyA== X-UI-Out-Filterresults: notjunk:1;V01:K0:LXSPaPqW6ws=:u0IJQPWHRA/S/vsM2bDLSo b9ZLqeS3a7E3S7C0iS8oQCNSRuV4Ci2xG1Jd0sLEWeU6yMvvK98LKRg7Sni7rLfg3BWSsXBOb 5OxWTE1duvRtf2llWJFkKetNW8hZYgZI5AnI2R2KqGtoqrHl3qlOSYZ3ONvSVskz8DWKetsS8 szjLel0I3wt4gfr3Xyc9E+xd0IuaXQMBSZk1GluwXRtOM1H+vnMUb6kb3r0ZzetmSGS18aGIW Pu0HO6XjOnPoNOWzlcubZ/xKvg+3nj+ROB9qmF9HEzJLLo/X010Ndy1TsuaFu+Epe1pnxTFla bJhWdaIe9447S8lclJv8K0yvkDqSv7xOCBpATWryIxCfPOkPDoO8E62t9l+gR/m1XKXOqy9/H gPO6R0D13KjTdCVgsnl/92LzSaFLZ5fxf5vYwlgKpLOih5+yAm/N880XUopuYaMOnFAjH7SDJ XQeW1KSM95W8q/JLRg9rWR4ljtRZHFElaxQtV7iod127rqMWMnVbqtXjCA5ol6N0uub2NTcC8 8cU/vOtQGnz5xr18JwvsxBF6DGYC0KxOH6OOUarS6qhqTOj4APb5M34teXs/Yj9RtgjUFlelI i2Ukj9KRExRCublJY0eYIul8H55NjrUju8b9qZ7pZQfNXf0qsSaH+5CgqCIuiAzaXu8gVgiFT H1FrGu6zbu4Z24CJYu/XjGg6VIKMOJngOLAzEOm2y8FzaCO0TAJvqspR9yPCbe3YRqMPQFzMr 9rk6arRBp2aaoCor X-Pg-Spam-Score: -1.4 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org My first concern is compatibility with the SQL standard - not the performance issues. Summarising the actual thread and mail https://www.postgresql.org/message-id/CAJNY3ivGORG1JSjZmop6k_OCJiLop5UCrWkm6NtwEVZhZpFRUw%40mail.gmail.com (ff.) I want to state: - There are 3 (main) character data types: a) character with fixed length b) character with variable size and a fix upper length limit and c) character with variable size and undeclared (but implementation dependent) upper length limit. - Types a) and b) are named identical in the standard and in Postgres (CHAR/VARCHAR). Data type c) is named CLOB in the standard and TEXT in Postgres. Why this different wording, if there is no real difference between the terms? - Our documentation says that Postgres does not support feature T041 of the standard. But functions like LENGTH, LOWER, TRIM, UPPER, CONCATENATION, ... works well on TEXT. Do we have some people in the standardisation committees (ANSI, BSI, DIN, JISC, ...), who represents the Postgres interests at this level? Kind regards, Jürgen On 07.10.2016 15:19, Adrian Klaver wrote: > On 10/07/2016 12:25 AM, Pavel Stehule wrote: >> Hi >> >> 2016-10-07 9:10 GMT+02:00 Jürgen Purtz > >: >> >> a) What is the distinction between our data type TEXT and the >> SQL:2011 data type CLOB which we do not support (T041)? >> >> >> TEXT type is classic type - you can do any available operation directly >> there. You don't need special conversions. >> >> >> >> b) Is there a distinction between the two Postgres data types TEXT >> and "CHARACTER VARYING without specifying a length" - or are they >> only synonym terms without different functionalities and >> capabilities? >> >> >> TEXT and varchar are pretty same types - you cannot to set limit over >> TEXT type - only this is visible difference > > See also: > > https://www.postgresql.org/message-id/998.1474901921%40sss.pgh.pa.us > >> >> Regards >> >> Pavel >> >> >> >> Kind regards, Jürgen >> >> >> >> >> -- >> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org >> ) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-sql >> >> >> > > -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql