Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fASVZ-0002HT-LH for pgsql-docs@arkaria.postgresql.org; Mon, 23 Apr 2018 03:51:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fASVX-0003CL-QA for pgsql-docs@arkaria.postgresql.org; Mon, 23 Apr 2018 03:51:15 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fASVX-0003CC-8A for pgsql-docs@lists.postgresql.org; Mon, 23 Apr 2018 03:51:15 +0000 Received: from 99-153-64-76.uvs.austtx.sbcglobal.net ([99.153.64.76] helo=noel.decibel.org) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fASVI-0002np-7X for pgsql-docs@lists.postgresql.org; Mon, 23 Apr 2018 03:51:06 +0000 Received: from decina.attlocal.net (108-232-179-70.lightspeed.austtx.sbcglobal.net [108.232.179.70]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTPSA id 3ACF06D45D; Sun, 22 Apr 2018 22:50:53 -0500 (CDT) Subject: Re: bit-strings with white space To: Tom Lane , pauleg.carter@gmail.com Cc: pgsql-docs@lists.postgresql.org References: <152404531940.19373.17868808849072401262@wrigleys.postgresql.org> <26418.1524417492@sss.pgh.pa.us> From: Jim Nasby Message-ID: Date: Sun, 22 Apr 2018 22:50:50 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <26418.1524417492@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 4/22/18 12:18 PM, Tom Lane wrote: > regression=# select 'foo' > 'bar'; > ?column? > ---------- > foobar > (1 row) > > Perhaps there's something we could change to make this clearer, > but I'm not sure what. I had no idea you could do that. While there's probably some wordy description that could explain this, I think an example is probably the best bet. Are there any other data types that work like this? -- Jim C. Nasby, Data Architect jim@nasby.net 512.569.9461 (cell) http://jim.nasby.net