diff options
| author | Bruce Momjian | 2016-08-05 18:35:09 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2016-08-05 18:36:17 +0000 |
| commit | 5ebad9a580d8f80943fd7095db14621278cc009c (patch) | |
| tree | 80ba871f657d5fa5d6b02be55d07348e4b516031 /doc/src/sgml/lobj.sgml | |
| parent | a629330b2990c2e76cc8e45a78ede0920c16e0bf (diff) | |
docs: re-add spaces before units removed
This reverts the spaces before k/M/G/TB units removed for consistency in
commit ca0c37b56f4a80ad758774e34c86cc4335583d29.
Discussion: [email protected]
Diffstat (limited to 'doc/src/sgml/lobj.sgml')
| -rw-r--r-- | doc/src/sgml/lobj.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml index f83e9cee2bd..8726f0c7013 100644 --- a/doc/src/sgml/lobj.sgml +++ b/doc/src/sgml/lobj.sgml @@ -50,8 +50,8 @@ 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 4TB in size, whereas <acronym>TOAST</acronym>ed fields can be at - most 1GB. Also, reading and updating portions of a large object can be + up to 4 TB in size, whereas <acronym>TOAST</acronym>ed 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 <acronym>TOAST</acronym>ed field will read or write the whole value as a unit. </para> |