From 11a020eb6e4023a1570a2788ba22dd6aafbd02dc Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Thu, 28 Aug 2014 13:59:29 +0200 Subject: Allow escaping of option values for options passed at connection start. This is useful to allow to set GUCs to values that include spaces; something that wasn't previously possible. The primary case motivating this is the desire to set default_transaction_isolation to 'repeatable read' on a per connection basis, but other usecases like seach_path do also exist. This introduces a slight backward incompatibility: Previously a \ in an option value would have been passed on literally, now it'll be taken as an escape. The relevant mailing list discussion starts with 20140204125823.GJ12016@awork2.anarazel.de. --- doc/src/sgml/protocol.sgml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'doc/src') diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index e519ff96b90..a8a09e4f0ec 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -4734,7 +4734,10 @@ StartupMessage (F) set at backend start time might be listed. Such settings will be applied during backend start (after parsing the command-line options if any). The values will act as - session defaults. + session defaults. Spaces in option values need to be escaped + with a backslash (\). A literal backslash can be + passed by escaping it with another backslash + (i.e \\). -- cgit v1.2.3