summaryrefslogtreecommitdiff
path: root/src/backend/utils/time/combocid.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2024-01-02 11:56:02 -0500
committerRobert Haas <rhaas@postgresql.org>2024-01-02 12:05:41 -0500
commit0d9937d1185629a94bf43dd0768c8f4eb835c9f0 (patch)
tree3a4b5db3c8f3430daf7eda0f55672f7fbda6fcf3 /src/backend/utils/time/combocid.c
parent5c430f9dc559ecd3bda8bebf4854f3f8d8bd86f3 (diff)
Fix typos in comments and in one isolation test.
Dagfinn Ilmari Mannsåker, reviewed by Shubham Khanna. Some subtractions by me. Discussion: http://postgr.es/m/87le9fmi01.fsf@wibble.ilmari.org
Diffstat (limited to 'src/backend/utils/time/combocid.c')
-rw-r--r--src/backend/utils/time/combocid.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/time/combocid.c b/src/backend/utils/time/combocid.c
index 0e94bc93f74..192d9c1efc3 100644
--- a/src/backend/utils/time/combocid.c
+++ b/src/backend/utils/time/combocid.c
@@ -4,7 +4,7 @@
* Combo command ID support routines
*
* Before version 8.3, HeapTupleHeaderData had separate fields for cmin
- * and cmax. To reduce the header size, cmin and cmax are now overlayed
+ * and cmax. To reduce the header size, cmin and cmax are now overlaid
* in the same field in the header. That usually works because you rarely
* insert and delete a tuple in the same transaction, and we don't need
* either field to remain valid after the originating transaction exits.