diff options
| author | Robert Haas <rhaas@postgresql.org> | 2016-03-08 13:28:00 -0500 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2016-03-08 13:28:00 -0500 |
| commit | 272baaa538f7a3186ac0c03764a8af9c0f5c00ac (patch) | |
| tree | 8e83d48fde972313d3cef3df0caeeeddb470a223 | |
| parent | dcfecaae9e35afe4fb11304267f547141842447d (diff) | |
| download | postgresql-272baaa538f7a3186ac0c03764a8af9c0f5c00ac.tar.gz postgresql-272baaa538f7a3186ac0c03764a8af9c0f5c00ac.zip | |
Fix typo.
Masahiko Sawada
| -rw-r--r-- | doc/src/sgml/pgvisibility.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/pgvisibility.sgml b/doc/src/sgml/pgvisibility.sgml index 6a98b55949e..cdd6a6fc1e9 100644 --- a/doc/src/sgml/pgvisibility.sgml +++ b/doc/src/sgml/pgvisibility.sgml @@ -21,7 +21,7 @@ until such time as a tuple is inserted, updated, deleted, or locked on that page. The page-level <literal>PD_ALL_VISIBLE</literal> bit has the same meaning as the all-visible bit in the visibility map, but is stored - within the data page itself rather than a separate data tructure. These + within the data page itself rather than a separate data structure. These will normally agree, but the page-level bit can sometimes be set while the visibility map bit is clear after a crash recovery; or they can disagree because of a change which occurs after <literal>pg_visibility</> examines |