From 818ac8479b04e1fee7b6936f1ef2efb253bf9169 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Sat, 25 Nov 2006 22:44:48 +0000 Subject: [PATCH] Correct misspellings of kB. --- doc/src/sgml/config.sgml | 4 ++-- doc/src/sgml/runtime.sgml | 6 +++--- doc/src/sgml/storage.sgml | 10 +++++----- doc/src/sgml/wal.sgml | 4 ++-- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 457d9246f3..dfdb42f0c4 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -847,7 +847,7 @@ SET ENABLE_SEQSCAN TO OFF; 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 1becd1a959..4eaf2bab59 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,4 +1,4 @@ - + Operating System Environment @@ -680,7 +680,7 @@ psql: could not connect to server: No such file or directory options "SHMALL=8192" options "SHMMAX=\(SHMALL*PAGE_SIZE\)" - SHMALL is measured in 4KB pages, so a value of + 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 @@ -921,7 +921,7 @@ kern.sysv.shmall=1024 - SHMALL is measured in 4KB pages on this platform. + SHMALL is measured in 4 kB pages on this platform. diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml index ae1a11d52b..ac4225b7bd 100644 --- a/doc/src/sgml/storage.sgml +++ b/doc/src/sgml/storage.sgml @@ -1,4 +1,4 @@ - + @@ -188,7 +188,7 @@ Oversized-Attribute Storage Technique). PostgreSQL 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 @@ -261,7 +261,7 @@ regardless of the actual size of the represented value. The TOAST code is triggered only when a row value to be stored in a table is wider than BLCKSZ/4 -bytes (normally 2Kb). The TOAST code will compress and/or move +bytes (normally 2 kB). The TOAST code will compress and/or move field values out-of-line until the row value is shorter than 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 @@ -328,7 +328,7 @@ containing typical HTML pages and their URLs was stored in about half of the raw data size including the 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-TOASTed -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. @@ -361,7 +361,7 @@ an item is a row; in an index, an item is an index entry. Every table and index is stored as an array of 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 metapage diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index d720e81e16..99e505db90 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -1,4 +1,4 @@ - + Reliability and the Write-Ahead Log @@ -313,7 +313,7 @@ WAL logs are stored in the directory pg_xlog 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 access/xlog.h; 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 -- 2.40.0