Thread: backpatch for REL9_4_STABLE of commit 40482e606733675eb9e5b2f7221186cf81352da1

Hi,

I think this fixed is also required for REL9_4_STABLE.
Please confirm the attached patch.

Thanks and best regards,
Dang Minh Huong
NEC Solution Innovators, Ltd.
http://www.nec-solutioninnovators.co.jp/en/

On Mon, Feb 8, 2016 at 8:20 PM, Huong Dangminh
<huo-dangminh@ys.jp.nec.com> wrote:
> Hi,
>
> I think this fixed is also required for REL9_4_STABLE.
> Please confirm the attached patch.

Yes, this fix was missed for 9.4 stable branch during back patch
and it is available on all other supported branches.

Regards,
Hari Babu
Fujitsu Australia

On 2016-02-08 20:59:25 +1100, Haribabu Kommi wrote:
> On Mon, Feb 8, 2016 at 8:20 PM, Huong Dangminh
> <huo-dangminh@ys.jp.nec.com> wrote:
> > Hi,
> >
> > I think this fixed is also required for REL9_4_STABLE.
> > Please confirm the attached patch.
> 
> Yes, this fix was missed for 9.4 stable branch during back patch
> and it is available on all other supported branches.

Since this evidently was an omission, I backpatched the relevant commit
to 9.4. That seems prudent, given that the issue is documented to be
fixed there...

Thanks for the report.

Andres

On Mon, Feb 08, 2016 at 09:20:46AM +0000, Huong Dangminh wrote:
> I think this fixed is also required for REL9_4_STABLE.
> Please confirm the attached patch.

Sure thing, no idea where that cherry-pick got lost.

Thanks.

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL