aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2022-03-24 20:56:31 +0900
committerMichael Paquier <michael@paquier.xyz>2022-03-24 20:56:31 +0900
commitbbd4951b73ec5ba4356133140da19cf378a796fd (patch)
treecded5f00c476e93ac7d5216914c3b601643ecf70 /src/backend/executor/nodeModifyTable.c
parent127aea2a65cd89c1c28357c6db199683e219491e (diff)
downloadpostgresql-bbd4951b73ec5ba4356133140da19cf378a796fd.tar.gz
postgresql-bbd4951b73ec5ba4356133140da19cf378a796fd.zip
doc: Improve postgres command for shared_memory_size_in_huge_pages
The command used in the documentation to retrieve the value of the runtime-computed GUC shared_memory_size_in_huge_pages would also show to the user all the log messages generated by the postmaster before and after printing the wanted value. This can be confusing, as the wanted result could be masked with a lot of noise. One way to avoid those log messages is to use something like "-c log_min_messages=fatal" in the command (my idea, but that's not common knowledge). Rather than mentioning this option, suffix the command with a redirection of stderr to /dev/null, which is the stream location where the logs show up. This is enough to show only the GUC value to the user when copy-pasting the command. Reported-by: Magnus Hagander Author: Nathan Bossart Discussion: https://postgr.es/m/20220314173417.GA1020555@nathanxps13
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions