[HACKERS] Open 6.3 issues (fwd)

Here are the items. Can I remove any of them?

Looking over the list, the only major one I see is that pg_user is not
world-readable, and with Todd not responding, I am thinking I may need
to do some ripout. Right now, \d does not work for non-super-users.
Can you imagine the problem reports we will get on that?

Many of these items can be moved to the TODO list after the release.

---------------------------------------------------------------------------

ORDER BY NULLs problem?
pg_user not world-readable, no initdb password option(Todd Brandys)
make psql \d optionally user pg_user(Bruce)
optimizer memory exhaustion with many OR's
max tuple size patch(Darren)
Is GROUP BY duplicates fixed?
Do we have a self-join optimizer performance problem?
Get interfaces fixed for new protocol
Profiling improvements?
Do we have a problem with GROUP BY without ORDER BY?
Problem with tables >2Gb
Do we want to add timestamps to elog messages?
ScanKeyData missing initializations
Can we improve vacuum locking issues?
Alpha/64-bit issues, mkoidname() problem
'Can not write block blind' error on createdb and regression collision
Views on aggregates fail
large objects memory exhaustion
subselect issues, NOT IN (empty query)
Commit sgml document sources(Thomas)
Commit html documents(Thomas)
Commit postscript documents(Thomas)
Fix isinf.c irix port problem reported by Andrew(Marc)
Check triggers regression test(Vadim)
Check select_views regression test
Test ecpg new struct features(Michael)
Test big-endian/little-endian operation(Tatsuo?)?
Linux library issues?

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us