| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brandon Metcalf" <bmetcalf(at)nortel(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: backslashes in 8.3.3 |
| Date: | 2008-06-24 18:02:50 |
| Message-ID: | 3639.1214330570@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Brandon Metcalf" <bmetcalf(at)nortel(dot)com> writes:
> t == tgl(at)sss(dot)pgh(dot)pa(dot)us writes:
> t> Uh, no, that is certainly *not* the behavior you were getting in 8.1;
> t> 8.1's behavior corresponds to both switches off.
> OK. I'm confused. With 8.1.5 we never had to do anything special
> with backslashes. When we upgraded to 8.3.3, backslashes in our
> INSERTs caused problems until we turn _on_
> standard_conforming_strings.
Maybe something changed on the client side? 8.1 definitely does not have
standard_conforming_strings, but perhaps you had some client-side
code that compensated by inserting backslashes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-24 18:12:47 | Re: Probably been asked a hundred times before. |
| Previous Message | Scott Marlowe | 2008-06-24 18:02:05 | Re: Probably been asked a hundred times before. |