From: Abbas B. <abb...@en...> - 2014-02-27 16:35:53
|
On Wed, Feb 19, 2014 at 12:46 AM, David E. Wheeler <da...@ju...>wrote: > On Feb 16, 2014, at 11:13 PM, 鈴木 幸市 <ko...@in...> wrote: > > > 1.1 is not suffered by this. The bug was introduced during planner > code change to deal with PG planner code change (mainly from automatic > updatable views). > > I don’t understand. I get this error on 1.1, and Abbas says it is not > present in 1.2. That seems like an issue in 1.1 that might be fixable in a > 1.1.1 release, should there ever be one. Am I missing something? > Sorry for the confusion. We have currently no plans to release 1.1.1. Between 1.1 and 1.2 we have re-factored code in many areas and bug fixes are not easily back portable. > Best, > > David -- -- *Abbas* Architect Ph: 92.334.5100153 Skype ID: gabbasb www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/> *Follow us on Twitter* @EnterpriseDB Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community> |