Thread: Open 6.3 issues

Here they are.  Please tell me if I can remove any of them.  Unfixed
items get added to the TODO list after the final 6.3 release.


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

ORDER BY NULLs problem?
test new view permission code, install new pg_user view for use with \d
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?)?
REVOKE ALL ON pg_user FROM PUBLIC crashes if run many times


--
Bruce Momjian
maillist@candle.pha.pa.us

On Sat, 21 Feb 1998, Bruce Momjian wrote:

> Here they are.  Please tell me if I can remove any of them.  Unfixed
> items get added to the TODO list after the final 6.3 release.

> Get interfaces fixed for new protocol

JDBC is now using the new protocol.

--
Peter T Mount  petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk

Bruce Momjian wrote:
>
> ORDER BY NULLs problem?

Hadn't time to look, yet...

> optimizer memory exhaustion with many OR's

I reported that it can't be fixed for 6.3 - please, move it into
TODO now. Nevertheless, I could apply patch to prepqual.c to
free memory whenever it's possible...

> Is GROUP BY duplicates fixed?

I got two reports that current code is OK - remove it.

> Do we have a self-join optimizer performance problem?

Yes. Not sure that I'll have time...

> Do we have a problem with GROUP BY without ORDER BY?
                                     ^^^^^^^
Could you remind what the problem is ?

> Problem with tables >2Gb

I still suggest to add elog(ERROR) to mdextend()...

> Can we improve vacuum locking issues?

I would leave vacuum as is. Improving of vacuum was on my 6.3 TODO
list - it's 6.4 TODO now :)

> 'Can not write block blind' error on createdb and regression collision

I'm fixing buffer manager now...

> subselect issues, NOT IN (empty query)

Closed: NOT IN (empty) and all others Op ALL (empty) now
returns TRUE.

> Check triggers regression test(Vadim)

Fixed already.

> Check select_views regression test

Results can't be identical on all platforms => change second query with

SELECT name, #thepath FROM iexit ORDER BY 1, 2;

Vadim