Thread: [BUGS] BUG #14812: URI options cann't set with equal char.

[BUGS] BUG #14812: URI options cann't set with equal char.

From
digoal@126.com
Date:
The following bug has been logged on the website:

Bug reference:      14812
Logged by:          Zhou Digoal
Email address:      digoal@126.com
PostgreSQL version: 10beta4
Operating system:   CentOS 7.x x64
Description:

there is some confusion:

```
psql postgres://postgres@127.0.0.1:1921/postgres?options="-c TimeZone =
+10"

psql: extra key/value separator "=" in URI query parameter: "options"
```

but in document:

https://www.postgresql.org/docs/10/static/libpq-connect.html


options
Specifies command-line options to send to the server at connection start.
For example, setting this to -c geqo=off sets the session's value of the
geqo parameter to off. Spaces within this string are considered to separate
command-line arguments, unless escaped with a backslash (\); write \\ to
represent a literal backslash. For a detailed discussion of the available
options, consult Chapter 19.


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #14812: URI options cann't set with equal char.

From
Oleksandr Shulgin
Date:
On Tue, Sep 12, 2017 at 3:37 PM, <digoal@126.com> wrote:
```
psql postgres://postgres@127.0.0.1:1921/postgres?options="-c TimeZone =
+10"

psql: extra key/value separator "=" in URI query parameter: "options"
```

but in document:

https://www.postgresql.org/docs/10/static/libpq-connect.html


options
Specifies command-line options to send to the server at connection start.
For example, setting this to -c geqo=off sets the session's value of the
geqo parameter to off. Spaces within this string are considered to separate
command-line arguments, unless escaped with a backslash (\); write \\ to
represent a literal backslash. For a detailed discussion of the available
options, consult Chapter 19.

In the same document, under "33.1.1.2. Connection URIs":

Percent-encoding may be used to include symbols with special meaning in any of the URI parts.

Have you tried to replace "=" with "%3D" (and " " with "%20")?

Regards,
--
Alex

Re: [BUGS] BUG #14812: URI options cann't set with equal char.

From
德哥
Date:

It's OK, Thanks,I think our document can add this note in it.   



--
公益是一辈子的事,I'm Digoal,Just Do It.

At 2017-09-12 22:49:03, "Oleksandr Shulgin" <oleksandr.shulgin@zalando.de> wrote:
On Tue, Sep 12, 2017 at 3:37 PM, <digoal@126.com> wrote:
```
psql postgres://postgres@127.0.0.1:1921/postgres?options="-c TimeZone =
+10"

psql: extra key/value separator "=" in URI query parameter: "options"
```

but in document:

https://www.postgresql.org/docs/10/static/libpq-connect.html


options
Specifies command-line options to send to the server at connection start.
For example, setting this to -c geqo=off sets the session's value of the
geqo parameter to off. Spaces within this string are considered to separate
command-line arguments, unless escaped with a backslash (\); write \\ to
represent a literal backslash. For a detailed discussion of the available
options, consult Chapter 19.

In the same document, under "33.1.1.2. Connection URIs":

Percent-encoding may be used to include symbols with special meaning in any of the URI parts.

Have you tried to replace "=" with "%3D" (and " " with "%20")?

Regards,
--
Alex

Re: [BUGS] BUG #14812: URI options cann't set with equal char.

From
Bruce Momjian
Date:
On Wed, Sep 13, 2017 at 04:11:49PM +0800, 德哥 wrote:
> 
> It's OK, Thanks,I think our document can add this note in it.   

Yes, good suggestion.  Docs added, which can be viewed here:
http://momjian.us/pgsql_docs/libpq-connect.html#libpq-connstring

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs