Parameter problem

LOG: invalid value for parameter "max_stack_depth": 16384

Cause explanation: The maximum security depth occupied by a database process at runtime STACK. If it is found that a complex recursive operation or a complex function cannot be run properly, it is recommended to increase the value of this configuration appropriately. Solution: Log in to the server and modify /etc/security/limits.conf to increase the user's stack depth size (using the antdb user as an example).

antdb soft stack unlimited
antdb hard stack unlimited

ERROR: unrecognized configuration parameter "shared_buffers"

Cause explanation: In some scenarios, since the param information of adbmgr is not initialized, manually execute the above command to initialize it and then set the parameters. Solution: Log in to adbmgr and execute the following command.

flush param;

FATAL: could not create shared memory segment: Cannot allocate memory

Cause explanation: The shared_buffer setting is not reasonable and exceeds the system configuration of kernel.shmmax. Solution: It is recommended to reduce the shared_buffer value, or increase the kernel parameters, such as shmall, shmmax values. If the shared_buffer is set too large, it will be reported as Invalid argument.

FATAL: invalid value for parameter "shared_buffers": "222222GB" HINT: Value exceeds integer range.

FATAL: could not create semaphores: No space left on device

Cause explanation: The max_connections setting is not reasonable and exceeds the system configuration of kernel.sem. max_connections is the maximum number of connections, that is, the maximum number of connections allowed for clients to connect, increasing connections can allow more clients to access, but setting too large will also cause DB startup failure semget is a function to get signals, that is, get semaphore. The above-mentioned space does not mean that the disk space is not enough, but the space parameter is not enough when creating semaphores, and the system call parameter semget reports an error. Solution: Decrease max_connections, or increase kernel parameters, such as semmni, semmns, etc. 5.3 Login error

error while loading shared libraries: libpq.so.5: cannot open shared object file: No such file or directory

Cause explanation: Some special software or plugins only recognize .bashrc but not .bash_profile, so after adding it, log out of the terminal and log in again.

Solution: In the .bashrc environment variable, is the following environment variable LD_LIBRARY_PATH set.

export LD_LIBRARY_PATH=$ADB_HOME/lib:$LD_LIBRARY_PATH

##