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

Started by amul sulabout 10 years ago2 messages
#1amul sul
sul_amul@yahoo.co.in

Hi,

Uninitialized variable 'dtype' warning in date_in() is fix[1]commit link=> http://git.postgresql.org/pg/commitdiff/5c45d2f87835ccd3ffac338845ec79cab1b31a11 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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#2Andres Freund
andres@anarazel.de
In reply to: amul sul (#1)
Re: commit 5c45d2f need to be back-patch on branch 9.2 & before

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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers