From: | Kristofer Munn <kmunn(at)munn(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | LO Problem List (Can we get one) |
Date: | 1999-06-06 23:21:40 |
Message-ID: | Pine.LNX.4.04.9906061917140.14186-100000@dec.munn.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-06-07 00:04:31 | Re: [HACKERS] Priorities for 6.6 |
Previous Message | Jan Wieck | 1999-06-06 19:31:23 | Re: [HACKERS] INSERT into VIEW |