From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
---|---|
To: | "Egashira, Yusuke" <egashira(dot)yusuke(at)jp(dot)fujitsu(dot)com> |
Cc: | Alban Hertroys <haramrae(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Giuseppe Sacco <giuseppe(at)eppesuigoccas(dot)homedns(dot)org> |
Subject: | Re: Question about password character in ECPG's connection string |
Date: | 2019-08-29 11:34:23 |
Message-ID: | CAKoxK+5fRS3y4XTkEgmU7zDME7cXg0doX8O6w2BWDP6X06RJpg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 29, 2019 at 1:08 PM Egashira, Yusuke
<egashira(dot)yusuke(at)jp(dot)fujitsu(dot)com> wrote:
> According to my tests, I think that the ECPG's connection_option seems not to accept '&' character as password anyhow...
> ECPG CONNECT's connection_option seems to have some restricted characters.
As far as I understand from
<https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/interfaces/ecpg/ecpglib/connect.c;h=ec01f67b61d5e8f0b88f84346451d2135a78b777;hb=HEAD#l603>
unwanted characters are '&' and '='. Even if the connetion string
seems an URL, it is managed in plain text without any sort of
escaping.
> I hope to this limitation will be documented because it causes confusion.
If this is confirmed, I agree this should be documented.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | francis picabia | 2019-08-29 11:43:18 | Re: How to log 'user time' in postgres logs |
Previous Message | Egashira, Yusuke | 2019-08-29 11:08:37 | RE: Question about password character in ECPG's connection string |