From: Tom Lane <tgl@sss.pgh.pa.us>
To: egashira.yusuke@jp.fujitsu.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: About limitation characters in ECPG's connection string
In-reply-to: <156870909344.1258.5689825888175704861@wrigleys.postgresql.org>
References: <156870909344.1258.5689825888175704861@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Tue, 17 Sep 2019 08:31:33 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5383.1568735711.1@sss.pgh.pa.us>
Date: Tue, 17 Sep 2019 11:55:11 -0400
Message-ID: <5384.1568735711@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> Please add the note about the limitation characters in connection string.
> For example, I think that below explanation should be in the Parameter
> section of connection_target.

We put in a change about that last month:

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=756349c87

Although that hasn't yet propagated to any released branches,
you can see it in the "devel" version of that documentation page:

https://www.postgresql.org/docs/devel/ecpg-connect.html#ECPG-CONNECTING

> Note that this parameter does not allow the symbols with special meaning of
> the URI parts, e.g. "&" and "?". 

Hm, I agree that the options part doesn't accept "&", but I don't see
anything preventing use of a "?" there.

			regards, tom lane