On 18 May 2015 at 12:59, Tom Lane <t...@sss.pgh.pa.us> wrote:

> Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> > Marko Tiikkaja wrote:
> >> Any chance to get this fixed in time for 9.1.16?
>
> > I hope you had pinged some days earlier.  Here's a patch, but I will
> > wait until this week's releases have been tagged before pushing.
>
> Is this a recent regression, or has it been busted all along in those
> branches?
>
> If the former, maybe we should take the risk of fixing it today
> (the patch certainly looks safe enough).  But if it's been this
> way a long time and nobody noticed till now, I'd agree with waiting.
>

That's a very low risk fix. It's more like a should-have-been-a-basic-check.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Reply via email to