Large Objects

From: Dan Boitnott <dan(at)mcneese(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Large Objects
Date: 2004-12-27 16:39:48
Message-ID: EC42F2F9-5825-11D9-B847-000D932E24AA@mcneese.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I need to do some investigation into the way Postgres handles large
objects for a major project involving large objects. My questions are:
* Can large objects be stored within a field value or must they be
referenced by OID?
* Are large objects backed up in the normal way or does special
action have to be taken?
* If the objects are restored or migrated will they retain their OID?
* If not, is there another means of referencing them that would be
persistent through migrations?
* Is it practical/desirable to store files MIME-Encoded inside a
text field?
* The obvious advantages:
* definitely portable across migrations and backups
* based on universal technology
* easy to code
* easy to reference and version-control
* The obvious disadvantages:
* slow, Slow, SLOW
* significant increase in per-file storage requirements

Any help would be greatly appreciated. Hope I'm posting to the right
list.

Dan

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-12-27 17:02:24 Re: 8.0 rc2 Problem
Previous Message vinita bansal 2004-12-27 16:36:21 error : syntax error at or near $1 for over select rows