Re: BUG #4843: non standard use string literal warning in RAISE WARNING - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4843: non standard use string literal warning in RAISE WARNING
Date
Msg-id 12158.1244469455@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4843: non standard use string literal warning in RAISE WARNING  ("Regina" <lr@pcorp.us>)
List pgsql-bugs
"Regina" <lr@pcorp.us> writes:
> I'm not sure if this is a bug or expected behavior.  But in a new PostGIS
> function we are writing, we are getting a

> WARNING: nonstandard use of \' in a string literal HINT: Use  to write
> quotes in strings, or use the escape string syntax (E'...').

> With sections of the code that look like
> RAISE WARNING 'Not inserting \'%\' in \'%.%\' into geometry_columns: could
> not determine ndims', quote_ident(gcs.attname), quote_ident(gcs.nspname),
> quote_ident(gcs.relname);

> The same function on 8.3.7 does not do this.

This is an intended change: RAISE format strings are now processed the
same as any other string literal.  Personally I'd suggest using '' here
rather than \' --- more standard, more future-proof, etc.

(Hmm, there seems to be nothing about it in the release notes ... not
sure how we overlooked that.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Regina"
Date:
Subject: BUG #4843: non standard use string literal warning in RAISE WARNING
Next
From: Mark Kirkwood
Date:
Subject: Cursor with hold emits the same row more than once across commits in 8.3.7