commit 5c45d2f need to be back-patch on branch 9.2 & before

Lists: pgsql-hackers
From: amul sul <sul_amul(at)yahoo(dot)co(dot)in>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: commit 5c45d2f need to be back-patch on branch 9.2 & before
Date: 2015-12-29 11:22:52
Message-ID: 2078494614.4473566.1451388172179.JavaMail.yahoo@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi,

Uninitialized variable 'dtype' warning in date_in() is fix[1] on branch 9.3 & above, but not for 9.2 & older branches. I guess this should be back-patch.
[1] commit link=> http://git.postgresql.org/pg/commitdiff/5c45d2f87835ccd3ffac338845ec79cab1b31a11

Regards,
Amul Sul


From: Andres Freund <andres(at)anarazel(dot)de>
To: amul sul <sul_amul(at)yahoo(dot)co(dot)in>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: commit 5c45d2f need to be back-patch on branch 9.2 & before
Date: 2015-12-29 11:42:26
Message-ID: 20151229114226.x33xobhuve443w6i@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi,

On 2015-12-29 11:22:52 +0000, amul sul wrote:
> Uninitialized variable 'dtype' warning in date_in() is fix[1] on branch 9.3 & above, but not for 9.2 & older branches. I guess this should be back-patch.
> [1] commit link=> http://git.postgresql.org/pg/commitdiff/5c45d2f87835ccd3ffac338845ec79cab1b31a11

We don't routinely backpatch warnings. Often enough the benefit is not
worth the risk. In this case I'd possibly gone the other way, but given
it's a low frequency warning in old branches I'm not inclined to do so
today.

Andres