| From: | Jobin Augustine <jobinau(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: libpq parameter parsing problem |
| Date: | 2020-01-16 04:53:00 |
| Message-ID: | CANaTPsqek=nHK6aGHc1susp=+_EsWL+bH-BCNpz=7V1J-mn59Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>
>
> > Links to authoritative sources (perhaps an RFC in this case) would be
> > better.
>
> No objections to your suggestion in this case though. I can see
> Section 2.1 from RFC3986 for that:
> https://tools.ietf.org/html/rfc3986#section-2.1
>
> So, gathering all the feedback and my own tweaks, I finish with the
> attached (merely simplified).
> --
> Michael
>
+1
As an end-user, It it is very clear for me now.
Verified the new example :
$ psql "postgresql://user(at)localhost
:5433/mydb?options=-c%20synchronous_commit%3Doff"
Password for user user:
Pager usage is off.
psql (12.0 (Ubuntu 12.0-2.pgdg18.04+1), server 11.5)
Type "help" for help.
mydb=> show synchronous_commit;
synchronous_commit
--------------------
off
(1 row)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleksandr Shulgin | 2020-01-16 08:17:23 | Re: libpq parameter parsing problem |
| Previous Message | Michael Paquier | 2020-01-16 04:06:18 | Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema |