> fix problem when DEFAULT string for CHAR() is not same as column
I think I fixed that a while ago. I've forgotten which file was
involved, but I no longer see the symptom on my system.
> man pages/sgml synchronization (dump out man pages as postscript?)
We should synchronize the man pages and sgml for this release, if
possible, and then commit to using the sgml sources for man pages for
v6.5. After v6.4 is released, man pages (but not sgml) are frozen until
they can be generated from the sgml.
> remove PARSEDEBUG defines if not longer needed
OK. You really want those gone, don't you!
> use index with constants on functions
Not likely for v6.4. On my list for v6.5.
> SELECT oid @ oid @ oid FROM pg_user fails with parser error, not
> function error
What is the issue with this? The parser doesn't know how to group the
arguments and operators, so barfs. The only operators which have
explicit precedence are the plain standard ones (+,-,*,/ for math and
=,<,> for comparisons, and |,: for who-knows-what). Everything else
falls into the same precedence, higher than the comparison operators and
lower than the math ones. This includes, for example, "<=" which should
be the same precedence as the other comparison ops, but has higher
precedence at the moment.
> no min/max for oid type
Does this still need to be on the list? The guy who asked for it
actually needed something else...
- Tom