> > > remove PARSEDEBUG defines if not longer needed
> > OK. You really want those gone, don't you!
> I can move it to the TODO list, OK? :-)
No, leave it on the v6.4 FixIt list. This is the start of that list,
right?
> > > SELECT oid @ oid @ oid FROM pg_user fails with parser error, not
> > > function error
> Should I move this to the TODO list now?
Well, I don't know how you would fix it without rewriting the parser or
changing the associativity of generic operators. I would suggest leaving
it off the ToDo list altogether, unless someone can suggest a viable
solution. The example suggests it is a problem with OIDs or with the "@"
operator, not a fundamental feature of the yacc/bison parser.
> > > no min/max for oid type
> I can move some of the items off now, rather than wait until just
> before 6.4 to be released to move them. OK?
Yeah. Let's turn this list into the v6.4 FixIt list; you've done one for
every release I can remember and it has been very helpful.
Be sure to add the views problem to this list ;)
Also, add the html/hardcopy documentation since we will re-release the
User's Guide, Admin Guide, and Programmer's Guide.
- Tom
