From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
Cc: | Barry Lind <barry(at)xythos(dot)com>, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: lots of large objects and toast |
Date: | 2000-05-30 03:22:07 |
Message-ID: | 17751.959656927@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> writes:
>> There's never been much enthusiasm among the core developers for large
>> objects at all --- we see them as a poor substitute for allowing large
>> values directly. (The "TOAST" work scheduled for 7.1 will finally
>> resolve that issue, I hope.) So no one's felt like working on improving
>> the large-object implementation.
> On the practical side, say I want to insert/read a large amount of
> information into/from a TOAST field. How should I do it?
> Is there a pipe method where I can continuously print to/read from?
Not at the moment, but that's obviously going to be a necessary feature
if we want to make the existing flavor of large objects obsolete. There
have been some preliminary discussions about it --- AFAIR no one's laid
out a complete proposal yet.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brett W. McCoy | 2000-05-30 03:24:30 | Re: Postgresql usage clip. |
Previous Message | Ron Chmara | 2000-05-30 03:02:40 | Re: Postgresql usage clip. |