Re: Re: Large Objects

From: Adam Haberlach <adam(at)newsnipple(dot)com>
To: PostgreSQL general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: Large Objects
Date: 2000-09-22 05:11:39
Message-ID: 20000921221138.A7368@ricochet.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 21, 2000 at 10:30:31PM -0400, Tom Lane wrote:
> You may be wondering "why bother, given TOAST?" (TOAST is long-tuple
> support, for those who haven't been paying attention.) Although TOAST
> should make many uses of BLOBs obsolete, there will be lots of
> applications that don't get updated right away (if ever), and still some
> where BLOBs are a natural, unforced solution. So I think it's worth
> capturing this performance improvement. It's just a shame we didn't get
> round to it sooner when BLOBs were the only game in town.

On that note, since it seems that the large objects that I've
just started using aren't likely to go away right this moment (and
their interface works for what I'm doing anyway), what is a good way
to write backend functions in C that will deal with large objects?

I would like to write some backend routines that will do
things like resize, watermark, and cache graphics files. If I
pass an Oid into a function, how would I access its data?

--
Adam Haberlach | A billion hours ago, human life appeared on
adam(at)newsnipple(dot)com | earth. A billion minutes ago, Christianity
http://www.newsnipple.com | emerged. A billion Coca-Colas ago was
'88 EX500 | yesterday morning. -1996 Coca-Cola Ann. Rpt.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message James Cribb 2000-09-22 06:04:15 How to get PGconn inside a user-defined C function?
Previous Message Tom Lane 2000-09-22 03:01:51 Re: More index / search speed questions