Re: backslashes in 8.3.3

"Brandon Metcalf" <bmetcalf(at)nortel(dot)com> writes:
> t == tgl(at)sss(dot)pgh(dot)pa(dot)us writes:
> 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.

Uh, no, that is certainly *not* the behavior you were getting in 8.1;
8.1's behavior corresponds to both switches off.

> 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.

Fast shutdown means something sent SIGINT to the postmaster.
The only way I've heard for that to happen "accidentally" is
if you normally launch the postmaster by hand in a way that
leaves it attached to your terminal session --- then control-C
in that session would SIGINT the postmaster.

regards, tom lane