Skip site navigation (1) Skip section navigation (2)

Re: debug nonstandard use of \\ in a string literal

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Ivan Zolotukhin *EXTERN*" <ivan(dot)zolotukhin(at)gmail(dot)com>,<pgsql-general(at)postgresql(dot)org>
Subject: Re: debug nonstandard use of \\ in a string literal
Date: 2008-02-28 11:28:04
Message-ID: D960CB61B694CF459DCFB4B0128514C2F34772@exadv11.host.magwien.gv.at (view raw or flat)
Thread:
Lists: pgsql-general
Ivan Zolotukhin wrote:
> From time to time I face with these well-known warnings in the
> PostgreSQL log, i.e.
> 
> Feb 28 04:21:10 db7 postgres[31142]: [2-1] WARNING:  nonstandard use
> of escape in a string literal at character 62
> Feb 28 04:21:10 db7 postgres[31142]: [2-2] HINT:  Use the escape
> string syntax for escapes, e.g., E'\r\n'.
> 
> This is fine, everybody knows about that and our PL/PgSQL developers
> try to make use of escape syntax. But sometimes errors occur anyway
> (by developers mistakes or something). So the question is: how to
> debug these annoying messages when pretty big application causes them?
> Is it possible to have a look what exact queries produced them?

All I can think of is to set

log_statement=all
log_min_error_statement=WARNING
log_min_messages=WARNING

which will cause all statements and warnings to be logged.

This might of course generate a lot of output...

Yours,
Laurenz Albe

In response to

Responses

pgsql-general by date

Next:From: Sam MasonDate: 2008-02-28 11:35:59
Subject: Re: How to "paste two tables side-by-side"?
Previous:From: David FetterDate: 2008-02-28 10:01:13
Subject: Re: dbi_link and dbi:ODBC

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group