Re: BUG #15373: null / utf-8

From: 'Bruce Momjian' <bruce(at)momjian(dot)us>
To: André Hänsel <andre(at)webkr(dot)de>
Cc: orchideric(at)yahoo(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15373: null / utf-8
Date: 2018-09-21 23:55:30
Message-ID: 20180921235530.GB18319@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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(at)momjian(dot)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 +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-09-22 18:41:50 BUG #15395: Assert failure when using CURRENT OF with inheritance
Previous Message PG Bug reporting form 2018-09-21 09:21:12 BUG #15394: Conflict between recovery thread and client queries on a hot standby replica