On 26 Oct 2015 4:55 PM, David G. Johnston wrote:
> On Mon, Oct 26, 2015 at 5:33 PM, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>>wrote:
>
> felipe@felipegasper.com <mailto:felipe@felipegasper.com> writes:
> > When dumping a DB whose name has a backslash in it, I get a warning like:
>
> > ------
> > pg_dump: WARNING: nonstandard use of \\ in a string literal
> > LINE 1: ...) AS description FROM pg_database WHERE datname = 'i have / ...
> > ^
> > HINT: Use the escape string syntax for backslashes, e.g., E'\\'.
> > ------
>
> It took me some time to reproduce that, but I eventually realized that
> you must have standard_conforming_strings turned off in your database
> settings.
>
>
> â[...]
> â
>
>
> Yes. For one thing, there would immediately be zero chance of loading
> view definitions produced by pg_dump into any other DBMS,
>
>
> Ironic...âwe cannot write a standard conforming string out because we
> are concerned other databases will be unable to read it.
>
> The OP is advised to set "escape_string_warning" to "off" if they also
> wish to have "standard_conforming_strings" set to "off". The question
> then is whether we should do so during restore regardless of whether the
> user has done so.
The problem is that I donât control the DB server...
-FG
