From: | "Campbell, Lance" <lance(at)uiuc(dot)edu> |
---|---|
To: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Large Objects and Toast |
Date: | 2007-12-14 17:11:41 |
Message-ID: | B10E6810AC2A2F4EA7550D072CDE8760197E45@SAB-FENWICK.sab.uiuc.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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.
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.
When putting a reference to a large object in a table, should the type
of the reference object be OID?
Thanks,
Lance Campbell
Project Manager/Software Architect
Web Services at Public Affairs
University of Illinois
217.333.0382
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2007-12-14 17:12:52 | VACUUM FREEZE output more than double input |
Previous Message | Alvaro Herrera | 2007-12-14 17:11:27 | Re: viewing source code |