Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZsN2A-0008TH-Mx for pgsql-docs@arkaria.postgresql.org; Sat, 31 Oct 2015 03:40:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZsN29-0002tU-4o for pgsql-docs@arkaria.postgresql.org; Sat, 31 Oct 2015 03:40:49 +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.84) (envelope-from ) id 1ZsN1n-0002VA-NV for pgsql-docs@postgreSQL.org; Sat, 31 Oct 2015 03:40:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZsN1l-0008Fb-DX for pgsql-docs@postgreSQL.org; Sat, 31 Oct 2015 03:40:26 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t9V3eNX3018814 for ; Fri, 30 Oct 2015 23:40:24 -0400 From: Tom Lane To: pgsql-docs@postgreSQL.org Subject: Obsolete advocacy for E-style strings in regexp documentation Date: Fri, 30 Oct 2015 23:40:23 -0400 Message-ID: <18813.1446262823@sss.pgh.pa.us> X-Pg-Spam-Score: -2.9 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org func.sgml has this bit near line 4660: Keep in mind that an escape's leading \ will need to be doubled when entering the pattern as an SQL string constant. For example: '123' ~ E'^\\d{3}' true This advice was surely helpful when it was written, but nowadays it's just advocating use of gratuitously non-SQL-standard string literal syntax. I propose just deleting the whole in HEAD, and maybe 9.5 too. A more aggressive approach would be to get rid of use of E-style literals in all/most of the documentation examples. I'm *not* advocating that, at least not yet. But this particular bit seems to be going out of its way to give obsolete advice. Thoughts? regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs