Commit 1309375e authored by Andres Freund's avatar Andres Freund

Fix two recently introduced grammar errors in mmgr/README.

These were introduced by me in f4e2d50c.

Reported-By: Tomas Vondra
Discussion: https://postgr.es/m/11adca69-be28-44bc-a801-64e6d53851e3@2ndquadrant.com
parent 2357c12b
...@@ -98,7 +98,7 @@ invoked to handle the operation, regardless. ...@@ -98,7 +98,7 @@ invoked to handle the operation, regardless.
----------------------------- -----------------------------
If all contexts were independent, it'd be hard to keep track of them, If all contexts were independent, it'd be hard to keep track of them,
especially in error cases. That is solved this by creating a tree of especially in error cases. That is solved by creating a tree of
"parent" and "child" contexts. When creating a memory context, the "parent" and "child" contexts. When creating a memory context, the
new context can be specified to be a child of some existing context. new context can be specified to be a child of some existing context.
A context can have many children, but only one parent. In this way 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 ...@@ -383,8 +383,8 @@ precede the MemoryContext. This means the only overhead implied by
the memory context mechanism is a pointer to its context, so we're not the memory context mechanism is a pointer to its context, so we're not
constraining context-type designers very much. constraining context-type designers very much.
Given this, routines like pfree their corresponding context with an Given this, routines like pfree determine their corresponding context
operation like (although that is usually encapsulated in with an operation like (although that is usually encapsulated in
GetMemoryChunkContext()) GetMemoryChunkContext())
MemoryContext context = *(MemoryContext*) (((char *) pointer) - sizeof(void *)); MemoryContext context = *(MemoryContext*) (((char *) pointer) - sizeof(void *));
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment