Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit bb46d42

Browse files
committed
Consistent spacing for lengthy error messages
Also, we removed the display of the current value of max_connections/MaxBackends from some messages earlier, because it was confusing, so do that in the remaining one as well.
1 parent a937b07 commit bb46d42

File tree

2 files changed

+4
-6
lines changed

2 files changed

+4
-6
lines changed

src/backend/port/sysv_sema.c

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -116,16 +116,14 @@ InternalIpcSemaphoreCreate(IpcSemaphoreKey semKey, int numSems)
116116
(unsigned long) semKey, numSems,
117117
IPC_CREAT | IPC_EXCL | IPCProtection),
118118
(errno == ENOSPC) ?
119-
errhint("This error does *not* mean that you have run out of disk space.\n"
119+
errhint("This error does *not* mean that you have run out of disk space. "
120120
"It occurs when either the system limit for the maximum number of "
121121
"semaphore sets (SEMMNI), or the system wide maximum number of "
122122
"semaphores (SEMMNS), would be exceeded. You need to raise the "
123123
"respective kernel parameter. Alternatively, reduce PostgreSQL's "
124-
"consumption of semaphores by reducing its max_connections parameter "
125-
"(currently %d).\n"
124+
"consumption of semaphores by reducing its max_connections parameter.\n"
126125
"The PostgreSQL documentation contains more information about "
127-
"configuring your system for PostgreSQL.",
128-
MaxBackends) : 0));
126+
"configuring your system for PostgreSQL.") : 0));
129127
}
130128

131129
return semId;

src/backend/port/sysv_shmem.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ InternalIpcMemoryCreate(IpcMemoryKey memKey, Size size)
173173
"memory configuration.",
174174
(unsigned long) size) : 0,
175175
(errno == ENOSPC) ?
176-
errhint("This error does *not* mean that you have run out of disk space. "
176+
errhint("This error does *not* mean that you have run out of disk space. "
177177
"It occurs either if all available shared memory IDs have been taken, "
178178
"in which case you need to raise the SHMMNI parameter in your kernel, "
179179
"or because the system's overall limit for shared memory has been "

0 commit comments

Comments
 (0)