Re: parse mistake in ecpg connect string

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: "wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com" <wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com>, "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-11 20:23:31
Message-ID: 1484516.1613075011@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> writes:
> 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.

Pushed with a little more work on the documentation.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2021-02-11 20:32:45 Re: Proposal: Save user's original authenticated identity for logging
Previous Message Andrew Dunstan 2021-02-11 20:04:17 Re: Tightening up allowed custom GUC names