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/lo-intro.html | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/src/sgml/html/lo-intro.html (limited to 'doc/src/sgml/html/lo-intro.html') diff --git a/doc/src/sgml/html/lo-intro.html b/doc/src/sgml/html/lo-intro.html new file mode 100644 index 0000000..a77e633 --- /dev/null +++ b/doc/src/sgml/html/lo-intro.html @@ -0,0 +1,18 @@ + +35.1. Introduction
35.1. Introduction
Prev UpChapter 35. Large ObjectsHome Next

35.1. Introduction

+ All large objects are stored in a single system table named pg_largeobject. + Each large object also has an entry in the system table pg_largeobject_metadata. + Large objects can be created, modified, and deleted using a read/write API + that is similar to standard operations on files. +

+ PostgreSQL also supports a storage system called + “TOAST”, + which automatically stores values + larger than a single database page into a secondary storage area per table. + This makes the large object facility partially obsolete. One + remaining advantage of the large object facility is that it allows values + up to 4 TB in size, whereas TOASTed fields can be at + most 1 GB. Also, reading and updating portions of a large object can be + done efficiently, while most operations on a TOASTed + field will read or write the whole value as a unit. +

Prev Up Next
Chapter 35. Large Objects Home 35.2. Implementation Features
\ No newline at end of file -- cgit v1.2.3