Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 674159FB561 for ; Sat, 21 Oct 2006 15:14:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 02123-07-2 for ; Sat, 21 Oct 2006 18:12:24 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 382579FB5E0 for ; Sat, 21 Oct 2006 14:15:59 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9LHFuCM026236; Sat, 21 Oct 2006 13:15:57 -0400 (EDT) To: Alvaro Herrera cc: pgsql-docs@postgresql.org Subject: Re: Outdated note In-reply-to: <20061020163942.GG6718@alvh.no-ip.org> References: <20061020163942.GG6718@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Fri, 20 Oct 2006 13:39:42 -0300" Date: Sat, 21 Oct 2006 13:15:56 -0400 Message-ID: <26235.1161450956@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/34 X-Sequence-Number: 3755 Alvaro Herrera writes: > On 4.1.2.1. String Constants, the following note appears: > Note: While ordinary strings now support C-style backslash escapes, > future versions will generate warnings for such usage and eventually > treat backslashes as literal characters to be standard-conforming. > That future version is 8.2, so the note should be updated to reflect it. Done; I ended up rewriting the whole subsection. I notice though that the following subsection about dollar quoting could really do with some rework too, because it implicitly assumes that backslashes are special in ordinary string literals. The example it gives to show the usefulness of dollar quoting for nested literals is really not very compelling at all if backslashes aren't special :-(. Can anyone come up with a better example that depends only on avoiding multiplied single quotes? regards, tom lane