pgsql: Allow escaping of option values for options passed at connection

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Allow escaping of option values for options passed at connection
Date: 2014-08-28 12:02:02
Message-ID: E1XMyOw-0001sG-4T@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)GJ12016(at)awork2(dot)anarazel(dot)de(dot)

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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2014-08-28 12:11:33 Re: pgsql: Allow units to be specified in relation option setting value.
Previous Message Fujii Masao 2014-08-28 07:15:35 pgsql: Allow units to be specified in relation option setting value.