1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.1beta1 Documentation"
13
HREF="index.html"><LINK
16
HREF="largeobjects.html"><LINK
19
HREF="largeobjects.html"><LINK
21
TITLE="Implementation Features"
22
HREF="lo-implementation.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-04-27T21:20:33"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1beta1 Documentation</A
57
HREF="largeobjects.html"
67
HREF="largeobjects.html"
74
>Chapter 32. Large Objects</TD
81
HREF="largeobjects.html"
89
TITLE="Implementation Features"
90
HREF="lo-implementation.html"
105
>32.1. Introduction</A
108
> All large objects are placed in a single system table called
111
>pg_largeobject</CODE
116
> also supports a storage system called
123
> that automatically stores values
124
larger than a single database page into a secondary storage area per table.
125
This makes the large object facility partially obsolete. One
126
remaining advantage of the large object facility is that it allows values
127
up to 2 GB in size, whereas <ACRONYM
131
most 1 GB. Also, large objects can be randomly modified using a read/write
132
API that is more efficient than performing such operations using
144
SUMMARY="Footer navigation table"
155
HREF="largeobjects.html"
173
HREF="lo-implementation.html"
189
HREF="largeobjects.html"
197
>Implementation Features</TD
b'\\ No newline at end of file'