database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

Fix typos.

Browse Source 
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
This commit is contained in:
Amit Kapila
2019-05-26 18:28:18 +05:30
parent 41205719d3
commit 9679345f3c
21 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/charset.sgml
View File

@ -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.

2
doc/src/sgml/monitoring.sgml
View File

@ -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.

2
doc/src/sgml/storage.sgml
View File

@ -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