From: Tom Lane <tgl@sss.pgh.pa.us>
To: pauleg.carter@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: bit-strings with white space
In-reply-to: <152404531940.19373.17868808849072401262@wrigleys.postgresql.org>
References: <152404531940.19373.17868808849072401262@wrigleys.postgresql.org>
Comments: In-reply-to =?utf-8?q?PG_Doc_comments_form?=
 <noreply@postgresql.org>
	message dated "Wed, 18 Apr 2018 09:55:19 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26417.1524417492.1@sss.pgh.pa.us>
Date: Sun, 22 Apr 2018 13:18:12 -0400
Message-ID: <26418.1524417492@sss.pgh.pa.us>
Precedence: bulk

=?utf-8?q?PG_Doc_comments_form?= <noreply@postgresql.org> writes:
> Postgresql 9.6, section 4.1.2.5 says that bit-strings can spill over
> multiple lines, same as regular string constants. I tried SELECTing such and
> found that they may only contain characters '0' and '1'.

As indeed the text says.  What the continuation mention is talking
about is this syntax:

regression=# select b'10001'
     '00100';
  ?column?  
------------
 1000100100
(1 row)

which works like

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.

			regards, tom lane