Re: 8.4 open items list
От | Josh Berkus |
---|---|
Тема | Re: 8.4 open items list |
Дата | |
Msg-id | 49CD10D9.4000409@agliodbs.com обсуждение исходный текст |
Ответ на | Re: 8.4 open items list (Guillaume Smet <guillaume.smet@gmail.com>) |
Ответы |
Re: 8.4 open items list
Re: 8.4 open items list Re: 8.4 open items list Re: 8.4 open items list |
Список | pgsql-hackers |
All, > On Fri, Mar 27, 2009 at 2:58 AM, Robert Haas<robertmhaas@gmail.com> wrote: >> I think we should also boot everything in the "pre-existing bugs" >> category, I don't agree. I think we should fix as many of those as we can without holding up the release. Having been (briefly) in charge of Another Open Source Database's bug list, I've seen where ignoring pre-existing bugs can lead, and it's not at all pretty. These bugs strike me as especially pernicious and to need fixing before 8.4 release (but NOT before Beta): * GiST picksplit (maybe GIN too?) can fail * Perl/libxml incompatibility * BUG #4721: bad side-effects of limitingnumber of clauses that predtest will consider * BUG #4694: uppercase path problem on Windows This one is also really bad, but probably only Doc-patchable. However, can SQL/XML really be said to be core functionality if it only works in UTF-8? * BUG #4622: xpath only work in utf-8 server encoding I'll also take a stab at this one, because it looks easy: * contrib/intarray opclass definition needs updating And Magnus fixed this one: * Path separator consistency on Windows The other "existing" bugs I think relate to extreme corner cases (e.g. ENUMs of DOMAINS) and/or may be feature requests rather than bugs (e.g. Cover Density Ranking) so I think can safely be put off until 8.4.1 or later. --Josh Berkus
В списке pgsql-hackers по дате отправления: