| From: | Chris Bitmead <chris(at)bitmead(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | TOAST suggestion... |
| Date: | 2000-01-24 07:26:17 |
| Message-ID: | 388BFE98.E15320B5@bitmead.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Can I make a suggestion for toast? I don't know how much this is thought
about yet, but it seems like it would be a good idea if large object
support be re-implemented in terms of TOAST (when it is available).
Because current
large objects suck so much.
Can I suggest that the TOAST system should be implemented to allow for
random access?
So for example, to retrieve a whole data member, of course it looks
normal...
SELECT xxx from yyy;
But to retrieve a particular chunk....
SELECT PORTION(xxx, 65535, 131071) from yyy;
to retrieve the 2nd 64k chunk.
This could be useful for many sorts of apps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-01-24 09:47:23 | AW: [HACKERS] Some notes on optimizer cost estimates |
| Previous Message | Tom Lane | 2000-01-24 05:58:38 | Re: [HACKERS] Use of Indicies ... |