Peter T Mount <peter(at)retep(dot)org(dot)uk> writes:
>
> The object is stored using a table/index pair, and takes up more disk
> space than a single object.
>
How much more? And what about performance?
In fact I don't need very large objects. 64k or even 32k will suffice.
Could such not-so-large objects be implemented more effectively? It would
be very nice to have a new postgres type for this. The 8k limit is very
restrictive. What do postgres gurus think?
Aleksey
--
Aleksey Demakov
avd(at)gcom(dot)ru