Search Postgresql Archives

Re: backslashes in 8.3.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



t == tgl@xxxxxxxxxxxxx writes:

 t> "Brandon Metcalf" <bmetcalf@xxxxxxxxxx> writes:
 t> > t == tgl@xxxxxxxxxxxxx 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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux