LO Problem List (Can we get one) - Mailing list pgsql-hackers

From Kristofer Munn
Subject LO Problem List (Can we get one)
Date
Msg-id Pine.LNX.4.04.9906061917140.14186-100000@dec.munn.com
Whole thread Raw
Responses Re: [HACKERS] LO Problem List (Can we get one)
List pgsql-hackers
Greetings once again.  I've been following recent threads on problems with
large objects and the possibility of plans for unlimited-size tuples in
version 6.6 (as a replacement).  I was wondering if there was a list of
all the Large Object known problems/limitations/drawbacks as of 6.5.  
This would include everything from any remaining memory leaks to the
performance hits resulting from having all the files in one directory to
the lack of a way to get a list of all existing LOs for dumping (or
cleanup).  I like to think I've caught all the relevant concerns (I use
Large Objects extensively in a large application I will be deploying) but
it would be nice to have such a list as well as perhaps linking them to
the documentation.

Thanks...

- K

Kristofer Munn * http://www.munn.com/~kmunn/ * ICQ# 352499 * AIM: KrMunn 



pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: [HACKERS] Priorities for 6.6
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Priorities for 6.6