| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Rainer" <rainer(at)hamburg(dot)ccc(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4398: Backslashes get escaped despite of backslash_quote=off |
| Date: | 2008-09-04 15:51:42 |
| Message-ID: | 23710.1220543502@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Rainer" <rainer(at)hamburg(dot)ccc(dot)de> writes:
> Description: Backslashes get escaped despite of backslash_quote=off
Aren't you looking for standard_conforming_strings? backslash_quote is
something else entirely, and doesn't actually do anything at all when
backslash escaping is disabled.
> Two questions:
> 1. What I actually want: Shouldn't the second statement work by
> documentation without the escape flag?
No. standard_conforming_strings has nothing to do with the behavior of
LIKE (nor does backslash_quote). They just control the initial parsing
of SQL string literals.
> 2. What I do not understand: Why does the fourth statement return a result
> as backslash_quote is off?
It looks like a perfectly good match to me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rainer Glueck | 2008-09-04 16:41:42 | Re: BUG #4398: Backslashes get escaped despite of backslash_quote=off |
| Previous Message | Denis Mitin | 2008-09-04 15:48:26 | Re: BUG #4389: FATAL: could not reattach to shared memory(key=1804, addr=018E0000): 487 |