File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -98,7 +98,7 @@ invoked to handle the operation, regardless.
9898-----------------------------
9999
100100If 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
103103new context can be specified to be a child of some existing context.
104104A 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
383383the memory context mechanism is a pointer to its context, so we're not
384384constraining 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
388388GetMemoryChunkContext())
389389
390390 MemoryContext context = *(MemoryContext*) (((char *) pointer) - sizeof(void *));
You can’t perform that action at this time.
0 commit comments