Re: backslashes in 8.3.3
От
Brandon Metcalf
Тема
Re: backslashes in 8.3.3
Дата
Msg-id
Pine.LNX.4.58L.0806241143501.9186@cash.us.nortel.com
Ответ на
Re: backslashes in 8.3.3 (Tom Lane)
Список
Дерево обсуждения
backslashes in 8.3.3 "Brandon Metcalf" <bmetcalf@nortel.com>
Re: backslashes in 8.3.3 Tom Lane <tgl@sss.pgh.pa.us>
Re: backslashes in 8.3.3 "Brandon Metcalf" <bmetcalf@nortel.com>
Re: backslashes in 8.3.3 Tom Lane <tgl@sss.pgh.pa.us>
Re: backslashes in 8.3.3 "Brandon Metcalf" <bmetcalf@nortel.com>
Re: backslashes in 8.3.3 Tom Lane <tgl@sss.pgh.pa.us>
Re: backslashes in 8.3.3 "Brandon Metcalf" <bmetcalf@nortel.com>
Re: backslashes in 8.3.3 Tom Lane <tgl@sss.pgh.pa.us>
Re: backslashes in 8.3.3 "Brandon Metcalf" <bmetcalf@nortel.com>
Re: backslashes in 8.3.3 "Brandon Metcalf" <bmetcalf@nortel.com>
t == tgl@sss.pgh.pa.us writes: t> "Brandon Metcalf" writes: t> > t == tgl@sss.pgh.pa.us writes: t> > t> See standard_conforming_strings and escape_string_warning. t> > Excellent. I had missed the standard_conforming_strings and will turn t> > this on. Hold on. Yes, that did it. Thanks so much. t> Well, if your intent is to replicate 8.1's behavior, you should instead t> frob the other switch. I now have escape_string_warning = off and standard_conforming_strings = on in postgresql.conf and things are back to how they were. That is no warnings and backslashes treated literally. A related question, is it in any way possible that a control sequence could have been sent from a client that caused a fast shutdown? Our server log shows a fast shutdown request last night, but nobody manually issued such a request. -- Brandon
В списке pgsql-general по дате отправления