diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/charset.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/storage.sgml | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index 555d1b4ac63..a2a46c6ab3a 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -896,7 +896,7 @@ CREATE COLLATION french FROM "fr-x-icu"; equal only if they consist of the same byte sequence. Nondeterministic comparison may determine strings to be equal even if they consist of different bytes. Typical situations include case-insensitive comparison, - accent-insensitive comparison, as well as comparion of strings in + accent-insensitive comparison, as well as comparison of strings in different Unicode normal forms. It is up to the collation provider to actually implement such insensitive comparisons; the deterministic flag only determines whether ties are to be broken using bytewise comparison. diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index a179d6111e4..570ac5e06f7 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3556,7 +3556,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, </entry> </row> <row> - <entry><structfield>current_locked_pid</structfield></entry> + <entry><structfield>current_locker_pid</structfield></entry> <entry><type>bigint</type></entry> <entry> Process ID of the locker currently being waited for. diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml index c4bac87e80e..1047c77a635 100644 --- a/doc/src/sgml/storage.sgml +++ b/doc/src/sgml/storage.sgml @@ -960,7 +960,7 @@ data. Empty in ordinary tables.</entry> (that is, <structfield>t_natts</structfield> bits altogether). In this list of bits, a 1 bit indicates not-null, a 0 bit is a null. When the bitmap is not present, all columns are assumed not-null. - The object ID is only present if the <firstterm>HEAP_HASOID</firstterm> bit + The object ID is only present if the <firstterm>HEAP_HASOID_OLD</firstterm> bit is set in <structfield>t_infomask</structfield>. If present, it appears just before the <structfield>t_hoff</structfield> boundary. Any padding needed to make <structfield>t_hoff</structfield> a MAXALIGN multiple will appear between the null |