diff options
| author | Amit Kapila <akapila@postgresql.org> | 2022-05-31 14:37:41 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2022-05-31 14:37:41 +0530 |
| commit | 0a050ee000b6783ac4b78e9eadb47a4e72912672 (patch) | |
| tree | d548609137ba0ea0c9be68686aeb5c04cde03e39 | |
| parent | 0efa51357e0fe0fd69f0c27245ed7e68039b1ea8 (diff) | |
Fix typo in hash README.
Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+Pu-V22PiJF2ym9_NVZe-+qnycfyEX24dZm=7URWhDHJ3w@mail.gmail.com
| -rw-r--r-- | src/backend/access/hash/README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/hash/README b/src/backend/access/hash/README index a2b8697d3c7..13dc59c124a 100644 --- a/src/backend/access/hash/README +++ b/src/backend/access/hash/README @@ -570,7 +570,7 @@ consistency after a crash. To provide robustness, we write WAL for each of these operations. CREATE INDEX writes multiple WAL records. First, we write a record to cover -the initializatoin of the metapage, followed by one for each new bucket +the initialization of the metapage, followed by one for each new bucket created, followed by one for the initial bitmap page. It's not important for index creation to appear atomic, because the index isn't yet visible to any other transaction, and the creating transaction will roll back in the event of |