Re: Large object insert/update and oid use

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-general(at)postgresql(dot)org
Cc: Louis LeBlanc <db(at)keyslapper(dot)org>
Subject: Re: Large object insert/update and oid use
Date: 2004-01-31 20:13:20
Message-ID: 6931.1075580000@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Louis LeBlanc <db(at)keyslapper(dot)org> writes:
>> For instance you need to explicitly delete a
>> large object when you don't need it any more --- deleting a table row
>> doesn't in itself make referenced large objects go away.

> This still sounds like our current model except for the fact that the
> OID has to be explicitly deleted. I assume a trigger could be set up
> to perform this on the fly though?

Yeah, as long as you keep things simple (no multiple references to
BLOBs) you can just add an ON DELETE trigger to handle that.

Given that this model is close to what you're already doing, large
objects probably are the way to go. Good luck with it.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message elein 2004-01-31 20:16:30 Re: Two joins on same foreign key
Previous Message Ben 2004-01-31 20:11:19 Re: Are there commands to enquire about table structure?