> > 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.
Removed.
>
> > 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.
OK.
>
> > 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? :-)
>
> > use index with constants on functions
>
> Not likely for v6.4. On my list for v6.5.
OK.
>
> > 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.
Should I move this to the TODO list now?
>
> > 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...
I can move some of the items off now, rather than wait until just before
6.4 to be released to move them. OK?
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
