From 311bcfc6b3acdd6fd152798c7f287ddf74fa2a98 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 16 Apr 2024 21:46:48 +0200 Subject: Adding upstream version 15.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/catalog-pg-largeobject.html | 48 +++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 doc/src/sgml/html/catalog-pg-largeobject.html (limited to 'doc/src/sgml/html/catalog-pg-largeobject.html') diff --git a/doc/src/sgml/html/catalog-pg-largeobject.html b/doc/src/sgml/html/catalog-pg-largeobject.html new file mode 100644 index 0000000..66466b9 --- /dev/null +++ b/doc/src/sgml/html/catalog-pg-largeobject.html @@ -0,0 +1,48 @@ + +53.30. pg_largeobject
53.30. pg_largeobject
Prev UpChapter 53. System CatalogsHome Next

53.30. pg_largeobject

+ 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). +

+ Prior to PostgreSQL 9.0, there was no permission structure + associated with large objects. As a result, + pg_largeobject 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 + pg_largeobject_metadata + to obtain a list of large object OIDs. +

Table 53.30. pg_largeobject Columns

+ Column Type +

+

+ Description +

+ loid oid + (references pg_largeobject_metadata.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 might 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 might be missing, and might 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. +

Prev Up Next
53.29. pg_language Home 53.31. pg_largeobject_metadata
\ No newline at end of file -- cgit v1.2.3