git.postgresql.org Git - postgresql.git/commitdiff

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml

index 457d9246f3f8b9b891918dc7c67b5a1868415cce..dfdb42f0c4cf019ee95c36fbbe8062b6948144ec 100644 (file)

--- a/doc/src/sgml/config.sgml

+++ b/doc/src/sgml/config.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.96 2006年11月21日 01:23:37 tgl Exp $ -->

+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.97 2006年11月25日 22:44:48 petere Exp $ -->

<chapter Id="runtime-config">

<title>Server Configuration</title>

margin is needed because the stack depth is not checked in every

routine in the server, but only in key potentially-recursive routines

such as expression evaluation. The default setting is

- 2048 KB (two megabytes), which is conservatively small and unlikely

+ 2048 kB (two megabytes), which is conservatively small and unlikely

to risk crashes. However, it may be too small to allow execution

of complex functions.

Only superusers can change this setting.

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml

index 1becd1a959d472620a805cc4365a8b858107b3a7..4eaf2bab5918095c3a2c49994082b756d56f9730 100644 (file)

--- a/doc/src/sgml/runtime.sgml

+++ b/doc/src/sgml/runtime.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.373 2006年09月16日 00:30:15 momjian Exp $ -->

+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.374 2006年11月25日 22:44:48 petere Exp $ -->

<chapter Id="runtime">

<title>Operating System Environment</title>

options "SHMALL=8192"

options "SHMMAX=\(SHMALL*PAGE_SIZE\)"

</programlisting>

- <varname>SHMALL</> is measured in 4KB pages, so a value of

+ <varname>SHMALL</> is measured in 4 kB pages, so a value of

1024 represents 4 MB of shared memory. Therefore the above increases

the maximum shared memory area to 32 MB.

For those running 4.3 or later, you will probably also need to increase

</para>

<para>

- <varname>SHMALL</> is measured in 4KB pages on this platform.

+ <varname>SHMALL</> is measured in 4 kB pages on this platform.

</para>

<para>

diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml

index ae1a11d52bf06ed5120aaebe32bd983438efd008..ac4225b7bd73ae3289cc5d7c79e634c236b72d31 100644 (file)

--- a/doc/src/sgml/storage.sgml

+++ b/doc/src/sgml/storage.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.11 2006年06月18日 15:38:36 petere Exp $ -->

+<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.12 2006年11月25日 22:44:48 petere Exp $ -->

<chapter id="storage">

<para>

<productname>PostgreSQL</productname> uses a fixed page size (commonly

-8Kb), and does not allow tuples to span multiple pages. Therefore, it is

+8 kB), and does not allow tuples to span multiple pages. Therefore, it is

not possible to store very large field values directly. To overcome

this limitation, large field values are compressed and/or broken up into

multiple physical rows. This happens transparently to the user, with only

<para>

The <acronym>TOAST</> code is triggered only

when a row value to be stored in a table is wider than <literal>BLCKSZ/4</>

-bytes (normally 2Kb). The <acronym>TOAST</> code will compress and/or move

+bytes (normally 2 kB). The <acronym>TOAST</> code will compress and/or move

field values out-of-line until the row value is shorter than

<literal>BLCKSZ/4</> bytes or no more gains can be had. During an UPDATE

operation, values of unchanged fields are normally preserved as-is; so an

raw data size including the <acronym>TOAST</> table, and that the main table

contained only about 10% of the entire data (the URLs and some small HTML

pages). There was no run time difference compared to an un-<acronym>TOAST</>ed

-comparison table, in which all the HTML pages were cut down to 7Kb to fit.

+comparison table, in which all the HTML pages were cut down to 7 kB to fit.

</para>

</sect1>

<para>

Every table and index is stored as an array of <firstterm>pages</> of a

-fixed size (usually 8Kb, although a different page size can be selected

+fixed size (usually 8 kB, although a different page size can be selected

when compiling the server). In a table, all the pages are logically

equivalent, so a particular item (row) can be stored in any page. In

indexes, the first page is generally reserved as a <firstterm>metapage</>

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml

index d720e81e16c0b0a875432a6b97308a9246971216..99e505db905b27dafdbf4980a29af2d8d606bc8e 100644 (file)

--- a/doc/src/sgml/wal.sgml

+++ b/doc/src/sgml/wal.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.41 2006年10月23日 18:10:32 petere Exp $ -->

+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.42 2006年11月25日 22:44:48 petere Exp $ -->

<chapter id="wal">

<title>Reliability and the Write-Ahead Log</title>

<acronym>WAL</acronym> logs are stored in the directory

<filename>pg_xlog</filename> under the data directory, as a set of

segment files, normally each 16 MB in size. Each segment is divided into

- pages, normally 8 KB each. The log record headers are described in

+ pages, normally 8 kB each. The log record headers are described in

<filename>access/xlog.h</filename>; the record content is dependent

on the type of event that is being logged. Segment files are given

ever-increasing numbers as names, starting at