| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adam Haberlach <adam(at)newsnipple(dot)com> |
| Cc: | PostgreSQL general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Re: Large Objects |
| Date: | 2000-09-22 14:54:43 |
| Message-ID: | 26639.969634483@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adam Haberlach <adam(at)newsnipple(dot)com> writes:
> 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?
Call the routines in src/backend/libpq/be-fsstubs.c, which are the
backend support for lo_read and so forth.
Note that these routines are changing to "new function manager" call
style in 7.1, so you will need to tweak your calling code when you
update...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John McKown | 2000-09-22 15:11:40 | Re: one more word about rules |
| Previous Message | Denis Perchine | 2000-09-22 14:46:22 | Re: Re: Large Objects |