It's a PostgreSQL message, nothing to worry about. It's just a warning telling you that you will in a future version of postgresql be required to use the E'' syntax if you still want to escape strings. It's to make postgresql more SQL compliant. NOthing to worry about, it may even spit that at valid strings (if they contain \\).
On Tuesday 21 August 2007 23:27:22 Dan Langille wrote: > FYI: I encountered the following when running bscan from version > 2.0.3 using PostgreSQL 8.2.1 and FreeBSD 6.2. > > 21-Aug 17:05 bscan: End of file 336 on device "NEO 2000" (/dev/nsa0), > Volume "AHP675L3" > bscan: bscan.c:677 2,686,976 file records. At file:blk=336:377,119 > bytes=113,081,204,577 > bscan: bscan.c:677 2,719,744 file records. At file:blk=336:386,173 > bytes=113,664,987,054 > 21-Aug 17:12 bscan: End of file 337 on device "NEO 2000" (/dev/nsa0), > Volume "AHP675L3" > nWARNING: nonstandard use of \\ in a string literal > LINE 1: SELECT PathId FROM Path WHERE > Path='/data2/backups/host50a/d... > ^ > HINT: Use the escape string syntax for backslashes, e.g., E'\\'. > WARNING: nonstandard use of \\ in a string literal > > Does anyone recall if this has been encountered previously? The word > "nonstandard" does not appear in the 2.0.3 source code. Google leads > me to think it is a PostgreSQL message. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
