| From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Thomas Swan <tswan(at)olemiss(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: 7.2 items |
| Date: | 2001-06-27 10:31:58 |
| Message-ID: | Pine.BSO.4.10.10106270629520.7004-100000@spider.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 27 Jun 2001, Hannu Krosing wrote:
> Bruce Momjian wrote:
> >
> > > Bruce Momjian wrote:
> > > >
> > > > > Please, consider a BLOB column type without having to do lo_import,
> > > > > lo_export.
> > > >
> > > > Yep, big needed item.
> > >
> > > as we have now and unlimited rowlength it seems to be more of an
> > > interface issue than the actual implementation one (mod seek/read).
> > >
> > > Is there an ISO/ANSI SQL interface to BLOB's defined someplace ?
> >
> > Yes, clearly interface. Someone is working on code to insert/export
> > binary stuff using bytea and base64 encoding. Seems like a good idea.
>
> Will there also be support current file-like BLOB ops like seek and
> read(n) ?
Sure, via substring(). Unfortunately, TOASTed tuple must be detoasted
completely, and you cannot get any performance boost by, for example,
reading first 8k out of a 500k bytea value. All 500k must be detoasted
first.
-alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Pilosov | 2001-06-27 10:42:14 | Re: Non-trivial rewriting sql query |
| Previous Message | Alex Pilosov | 2001-06-27 10:29:32 | Re: functions returning records |