Re: Re: Large Objects - Mailing list pgsql-general

From Adam Haberlach
Subject Re: Re: Large Objects
Date
Msg-id 20000921221138.A7368@ricochet.net
Whole thread Raw
In response to Re: Re: Large Objects  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Large Objects  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@newsnipple.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: More index / search speed questions
Next
From: James Cribb
Date:
Subject: How to get PGconn inside a user-defined C function?