holds the data making up
. A large object is identified by an OID
assigned when it is created. Each large object is broken into
small enough to be conveniently stored as rows
The amount of data per page is defined to be
(which is currently
, or typically 2 kB).
9.0, there was no permission structure
associated with large objects. As a result,
was publicly readable and could be
used to obtain the OIDs (and contents) of all large objects in the system.
This is no longer the case; use
to obtain a list of large object OIDs.
Identifier of the large object that includes this page
Page number of this page within its large object (counting from zero)
Actual data stored in the large object.
This will never be more than
Each row of
for one page of a large object, beginning at
byte offset (
pageno * LOBLKSIZE
) within the object. The implementation
allows sparse storage: pages might be missing, and might be shorter than
bytes even if they are not the last page of the object.
Missing regions within a large object read as zeroes.