From 9679345f3c5ec071f63db358581e28f06c8744a7 Mon Sep 17 00:00:00 2001 From: Amit Kapila Date: Sun, 26 May 2019 18:28:18 +0530 Subject: Fix typos. Reported-by: Alexander Lakhin Author: Alexander Lakhin Reviewed-by: Amit Kapila and Tom Lane Discussion: https://postgr.es/m/7208de98-add8-8537-91c0-f8b089e2928c@gmail.com --- doc/src/sgml/charset.sgml | 2 +- doc/src/sgml/monitoring.sgml | 2 +- doc/src/sgml/storage.sgml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') 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, - current_locked_pid + current_locker_pid bigint 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. (that is, t_natts 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 HEAP_HASOID bit + The object ID is only present if the HEAP_HASOID_OLD bit is set in t_infomask. If present, it appears just before the t_hoff boundary. Any padding needed to make t_hoff a MAXALIGN multiple will appear between the null -- cgit v1.2.3