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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tang, Haiying" <tanghy(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>, "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-08 16:14:24
Message-ID: 626054.1612800864@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tang, Haiying" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com> writes:
> 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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-02-08 16:49:41 Re: Detecting pointer misalignment (was Re: pgsql: Implementation of subscripting for jsonb)
Previous Message Markus Wanner 2021-02-08 15:06:30 Re: repeated decoding of prepared transactions