RE: parse mistake in ecpg connect string - Mailing list pgsql-hackers

From kuroda.hayato@fujitsu.com
Subject RE: parse mistake in ecpg connect string
Date
Msg-id OSBPR01MB315784DF78E77460240DB145F58F9@OSBPR01MB3157.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: parse mistake in ecpg connect string  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses RE: parse mistake in ecpg connect string
List 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




pgsql-hackers by date:

Previous
From: "kuroda.hayato@fujitsu.com"
Date:
Subject: RE: parse mistake in ecpg connect string
Next
From: Amit Kapila
Date:
Subject: Re: Single transaction in the tablesync worker?