RE: Made ecpg compatibility mode and run-time behaviour options case insensitive

From: "Tang, Haiying" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "meskes(at)postgresql(dot)org" <meskes(at)postgresql(dot)org>
Subject: RE: Made ecpg compatibility mode and run-time behaviour options case insensitive
Date: 2021-02-09 00:42:18
Message-ID: 5b710e9ff6844824a21a38ee67bb6c44@G08CNEXMBPEKD05.g08.fujitsu.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Tuesday, February 9, 2021 1:14 AM

>> When reading code related ECPG I found 75220fb was committed in PG13 and master.
>> I don't know why it shouldn't be backpatched in PG12 or before.
>> Can anyone take a look at this and kindly tell me why.
>
>We don't usually back-patch things that aren't clear bug fixes.

Thanks for your kindly explanation. Get it now.

Regards,
Tang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2021-02-09 01:29:52 Re: Parallel INSERT (INTO ... SELECT ...)
Previous Message Alexander Korotkov 2021-02-09 00:35:01 Re: Detecting pointer misalignment (was Re: pgsql: Implementation of subscripting for jsonb)