| PostgreSQL 8.1.8 Documentation | ||||
|---|---|---|---|---|
| Prev | Fast Backward | Chapter 42. System Catalogs | Fast Forward | Next |
The catalog pg_largeobject holds the data making up "large objects". A large object is identified by an OID assigned when it is created. Each large object is broken into segments or "pages" small enough to be conveniently stored as rows in pg_largeobject. The amount of data per page is defined to be LOBLKSIZE (which is currently BLCKSZ/4, or typically 2 kB).
Table 42-21. pg_largeobject Columns
| Name | Type | References | Description |
|---|---|---|---|
| loid | oid | Identifier of the large object that includes this page | |
| pageno | int4 | Page number of this page within its large object (counting from zero) | |
| data | bytea | Actual data stored in the large object. This will never be more than LOBLKSIZE bytes and may be less. |
Each row of pg_largeobject holds data for one page of a large object, beginning at byte offset (pageno * LOBLKSIZE) within the object. The implementation allows sparse storage: pages may be missing, and may be shorter than LOBLKSIZE bytes even if they are not the last page of the object. Missing regions within a large object read as zeroes.
No comments could be found for this page.
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
In order to submit a comment, you must have a community account.
* denotes required field