RE: parse mistake in ecpg connect string

From: "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: "wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com" <wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com>
Cc: "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Subject: RE: parse mistake in ecpg connect string
Date: 2021-02-09 07:38:17
Message-ID: TYAPR01MB3168981BF366FAE9C5C0A1EAF58E9@TYAPR01MB3168.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Wang, Horiguchi-san,

> > How about the attached?
>
> I think, this patch is good.

I agree. The backward compatibility is violated in the doc, but maybe no one take care.

> Maybe we can create a new thread to talk about how ecpg support ipv6

+1

Best Regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tsunakawa.takay@fujitsu.com 2021-02-09 07:47:05 RE: [POC] Fast COPY FROM command for the table with foreign partitions
Previous Message Peter Smith 2021-02-09 07:37:12 Re: Single transaction in the tablesync worker?