Skip to content

Commit 1309375

Browse files
committed
Fix two recently introduced grammar errors in mmgr/README.
These were introduced by me in f4e2d50. Reported-By: Tomas Vondra Discussion: https://postgr.es/m/11adca69-be28-44bc-a801-64e6d53851e3@2ndquadrant.com
1 parent 2357c12 commit 1309375

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/backend/utils/mmgr/README

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ invoked to handle the operation, regardless.
9898
-----------------------------
9999

100100
If all contexts were independent, it'd be hard to keep track of them,
101-
especially in error cases. That is solved this by creating a tree of
101+
especially in error cases. That is solved by creating a tree of
102102
"parent" and "child" contexts. When creating a memory context, the
103103
new context can be specified to be a child of some existing context.
104104
A context can have many children, but only one parent. In this way
@@ -383,8 +383,8 @@ precede the MemoryContext. This means the only overhead implied by
383383
the memory context mechanism is a pointer to its context, so we're not
384384
constraining context-type designers very much.
385385

386-
Given this, routines like pfree their corresponding context with an
387-
operation like (although that is usually encapsulated in
386+
Given this, routines like pfree determine their corresponding context
387+
with an operation like (although that is usually encapsulated in
388388
GetMemoryChunkContext())
389389

390390
MemoryContext context = *(MemoryContext*) (((char *) pointer) - sizeof(void *));

0 commit comments

Comments
 (0)