Date: Fri, 21 Sep 2018 19:55:30 -0400
From: 'Bruce Momjian' <bruce@momjian.us>
To: =?iso-8859-1?Q?Andr=E9_H=E4nsel?= <andre@webkr.de>
Cc: orchideric@yahoo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15373: null / utf-8
Message-ID: <20180921235530.GB18319@momjian.us>
References: <153642745785.23144.1699125571356845227@wrigleys.postgresql.org>
 <20180908173648.GJ28811@momjian.us>
 <12e601d447ac$345994a0$9d0cbde0$@webkr.de>
 <20180908203619.GA8672@momjian.us>
 <20180914022033.GD23686@momjian.us>
 <1cb801d44c03$299b8d60$7cd2a820$@webkr.de>
 <20180914194917.GA22477@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20180914194917.GA22477@momjian.us>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

On Fri, Sep 14, 2018 at 03:49:17PM -0400, 'Bruce Momjian' wrote:
> On Fri, Sep 14, 2018 at 10:15:48AM +0200, André Hänsel wrote:
> > Bruce Momjian wrote: 
> > > I have developed the attached documentation patch to remove the E''
> > > syntax.  standard_conforming_strings defaulted to 'on' in PG 9.1.
> > 
> > On https://www.postgresql.org/docs/current/static/arrays.html, there
> > is a note at the bottom with an example currently using the C-style
> > escape syntax. Your patch changes that, as agreed, but then the text
> > of the note, as it is at the moment, doesn't make sense anymore
> > because the note is about the doubling of backslashes that you have
> > with C-style escape string literals.
> 
> Wow, good you saw that.  I removed that entire paragraph since there is
> no longer double-escape evaluation by default.  Updated patch attached.

Patch applied through 9.3.  Thanks for the report.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +