| From: | "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Kyotaro Horiguchi' <horikyota(dot)ntt(at)gmail(dot)com>, "wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com" <wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: parse mistake in ecpg connect string |
| Date: | 2021-02-08 03:25:58 |
| Message-ID: | OSBPR01MB315784DF78E77460240DB145F58F9@OSBPR01MB3157.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Horiguchi-san,
My response crossed in the e-mail with yours. Sorry.
> FWIW, directly embedding /unixsocket/path syntax in a URL is broken in
> the view of URI. It is the reason why the current connection URI takes
> the way shown above. So I think we want to remove that code rather
> than to fix it.
I didn't know such a phenomenon. If other codes follow the rule,
I agree yours.
Digress from the main topic, but the following cannot be accepted for the precompiler.
This should be fixed, isn't it?
EXEC SQL CONNECT TO postgres@/tmp:5432;
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-02-08 03:40:21 | Re: Single transaction in the tablesync worker? |
| Previous Message | kuroda.hayato@fujitsu.com | 2021-02-08 03:02:26 | RE: parse mistake in ecpg connect string |