Skip to content
Snippets Groups Projects
Commit 50271fc9 authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files

Fix misspellings of GB.

parent 818ac847
Branches
Tags
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/src/sgml/release.sgml
+ 2
− 2
View file @ 50271fc9
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.486 2006/11/25 07:03:57 neilc Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.487 2006/11/25 22:55:59 petere Exp $ -->
<!-- <!--
   
Typical markup: Typical markup:
...@@ -12078,7 +12078,7 @@ On some platforms, building with -fstrict-aliasing causes bugs. ...@@ -12078,7 +12078,7 @@ On some platforms, building with -fstrict-aliasing causes bugs.
</para></listitem> </para></listitem>
<listitem><para>Make pg_restore handle 64-bit off_t correctly</para> <listitem><para>Make pg_restore handle 64-bit off_t correctly</para>
<para> <para>
This bug prevented proper restoration from archive files exceeding 4Gb. This bug prevented proper restoration from archive files exceeding 4 GB.
</para></listitem> </para></listitem>
<listitem><para>Make contrib/dblink not assume that local and remote type OIDs <listitem><para>Make contrib/dblink not assume that local and remote type OIDs
match (Joe)</para></listitem> match (Joe)</para></listitem>
......
doc/src/sgml/storage.sgml
+ 3
− 3
View file @ 50271fc9
<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.12 2006/11/25 22:44:48 petere Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.13 2006/11/25 22:55:59 petere Exp $ -->
<chapter id="storage"> <chapter id="storage">
...@@ -138,7 +138,7 @@ Avoid assuming that filenode and table OID are the same. ...@@ -138,7 +138,7 @@ Avoid assuming that filenode and table OID are the same.
</caution> </caution>
<para> <para>
When a table or index exceeds 1Gb, it is divided into gigabyte-sized When a table or index exceeds 1 GB, it is divided into gigabyte-sized
<firstterm>segments</>. The first segment's file name is the same as the <firstterm>segments</>. The first segment's file name is the same as the
filenode; subsequent segments are named filenode.1, filenode.2, etc. filenode; subsequent segments are named filenode.1, filenode.2, etc.
This arrangement avoids problems on platforms that have file size limitations. This arrangement avoids problems on platforms that have file size limitations.
...@@ -212,7 +212,7 @@ value, but in some cases more efficient approaches are possible.) ...@@ -212,7 +212,7 @@ value, but in some cases more efficient approaches are possible.)
<para> <para>
<acronym>TOAST</> usurps the high-order two bits of the varlena length word, <acronym>TOAST</> usurps the high-order two bits of the varlena length word,
thereby limiting the logical size of any value of a <acronym>TOAST</>-able thereby limiting the logical size of any value of a <acronym>TOAST</>-able
data type to 1Gb (2<superscript>30</> - 1 bytes). When both bits are zero, data type to 1 GB (2<superscript>30</> - 1 bytes). When both bits are zero,
the value is an ordinary un-<acronym>TOAST</>ed value of the data type. One the value is an ordinary un-<acronym>TOAST</>ed value of the data type. One
of these bits, if set, indicates that the value has been compressed and must of these bits, if set, indicates that the value has been compressed and must
be decompressed before use. The other bit, if set, indicates that the value be decompressed before use. The other bit, if set, indicates that the value
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment