> OK, we have most of the open items fixed. Marc, can you check on number
> 4, and Thomas, please apply your patch for item 3. We can then package
> a patch and close 6.3.*.
>
> > indexes not used that were used in 6.2(fixed)
> > memory leak in backend when run on simple queries(fixed)
> > negative sign causing problems in various areas, like float4 & shortint
> > configure assert checking is reversed
> > UNION crashes on ORDER BY or DISTINCT(already fixed in source tree)
How do we want to package the patches? Shall we assemble the relevant
patches as we did p1-p7 for v6.2.1? There were reports of problems or
difficulties from some people regarding the 6.3->6.3.1 patch, which is
probably pretty complex. Also, there are some changes in the source
tree, like the char2-16 removal, which should not appear until v6.4.
So, I'd recommend that we take the individual patches fixing each
problem, apply them to a clean v6.3.1, run regression tests (since those
apparently broke in v6.3.1) and then release that set of patches at one
time.
I'd be willing to do the regression testing and then pass the patches
back for posting. Comments?
- Tom
