From: | "Usama Dar" <munir(dot)usama(at)gmail(dot)com> |
---|---|
To: | "Campbell, Lance" <lance(at)uiuc(dot)edu> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Large Objects and Toast |
Date: | 2007-12-16 20:33:58 |
Message-ID: | ff0e67090712161233x1a998d36w81b5b4eb62112d40@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Dec 14, 2007 10:11 PM, Campbell, Lance <lance(at)uiuc(dot)edu> wrote:
> PostgreSQL: 8.2
>
>
>
> My understanding is that when one creates a large object there is no way
> to link the large object to a field in a table so that cascading delete can
> occur. Is this correct? My understanding is that you have to manually
> delete the large object.
>
Yes, but you can setup a trigger to do that for you i think.
>
>
> I also read something about the OID ID being limited in size. What is the
> size limit of this OID type? I am sure that it is bigger than the number of
> files that I would be uploaded into my db; but I just want to get an idea of
> the range.
>
Oid is an unsigned integer in postgres IIRC.
--
Usama Munir Dar http://linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar
From | Date | Subject | |
---|---|---|---|
Next Message | andrew | 2007-12-16 20:45:02 | Re: update 600000 rows |
Previous Message | Gregory Stark | 2007-12-16 20:06:47 | Re: libgcc double-free, backend won't die |