From: Palak Chaturvedi <palakchaturvedi2843@gmail.com>
Subject: [PATCH] shmem: distinguish mprotect failure messages

Refresh the earlier follow-up for the complete series.
---
diff --git a/src/backend/port/sysv_shmem.c b/src/backend/port/sysv_shmem.c
index c052776e94c..179ceab57ff 100644
--- a/src/backend/port/sysv_shmem.c
+++ b/src/backend/port/sysv_shmem.c
@@ -1200,7 +1200,8 @@ PGSharedMemoryProtect(void *rw_start, void *rw_end, void *prot_end)
 		if (mprotect(rw_start, (char *) rw_end - (char *) rw_start,
 					 PROT_READ | PROT_WRITE) != 0)
 		{
-			ereport(WARNING, errmsg("could not protect shared memory: %m"));
+			ereport(WARNING,
+					errmsg("could not make shared memory read-write: %m"));
 			return false;
 		}
 	}
@@ -1210,7 +1211,8 @@ PGSharedMemoryProtect(void *rw_start, void *rw_end, void *prot_end)
 		if (mprotect(rw_end, (char *) prot_end - (char *) rw_end,
 					 PROT_NONE) != 0)
 		{
-			ereport(WARNING, errmsg("could not protect shared memory: %m"));
+			ereport(WARNING,
+					errmsg("could not make reserved shared memory inaccessible: %m"));
 			return false;
 		}
 	}