pgsql: Allow escaping of option values for options passed at connection - Mailing list pgsql-committers

From Andres Freund
Subject pgsql: Allow escaping of option values for options passed at connection
Date
Msg-id E1XMyOw-0001sG-4T@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/11a020eb6e4023a1570a2788ba22dd6aafbd02dc

Modified Files
--------------
doc/src/sgml/protocol.sgml          |    5 +++-
src/backend/postmaster/postmaster.c |    3 +-
src/backend/utils/init/postinit.c   |   52 +++++++++++++++++++++++++----------
3 files changed, 43 insertions(+), 17 deletions(-)


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Allow units to be specified in relation option setting value.
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Allow units to be specified in relation option setting value.