Re: Fix for fetchone() and fetchmany() in Python interface

> > We only put major lowrisk fixes in 7.1.X releases, and this one is too
> > minor for the risk.  Sorry.
> >
>
> I think this patch is important enough -- it fixes an annoying broken
> call, with a two line patch that is quite localized. So, the risk level
> seems quite low. AFAICT, the worst thing this patch could do is keep
> fetch as broken, though perhaps in a different way. But, even then, I'm
> fairly confident that the patch is good, or at least better than what
> we've got, since we've already tried it out here, and found it to
> apparently fix the issue.

I am not actually making the decision myself.  Patching only major
problems with low-risk patches has always been our policy.  If you can
get others to agree, I will gladly apply it.

See the HISTORY file for a description of what is in 7.1.3.  You can see
they all follow that policy.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026