Skip to main content

Parameter list

KakaoCloud provides various parameters necessary for PostgreSQL configuration.
Some parameters support functions, expressions, and keywords. For more details, please refer to Parameter group > Expressions, functions, and keywords used in parameters.
Detailed information such as units, types, data formats, and editability of parameters can be found in the parameter group details view within the console.

Data format: Float

Parameters with a Float data format use the %.6g format when displaying values. This format only outputs up to 6 significant digits (excluding the decimal point). If the number of digits is exceeded, it is automatically rounded for display. Therefore, the value entered in the parameter group may differ from the actual value verified in the database.

Parameters to be careful of when modifying

These parameters require caution during modification because improper settings can affect the operation of the PostgreSQL service.

Process count limit

Due to its internal structure, PostgreSQL limits the total number of processes to 262,143 or fewer.
If the sum of autovacuum_max_workers, max_connections, max_wal_senders, and max_worker_processes exceeds 262,143, the configured values for these parameters will not be applied.

Memory parameters

Parameter nameDescriptionNotes when modifying
autovacuum_work_memMemory size for Autovacuum tasks
(-1 uses maintenance_work_mem)
Default -1: Uses the maintenance_work_mem value
Unavailable values: 0 ~ 1023
If a separate value is specified, total memory usage may increase up to autovacuum_work_mem x autovacuum_max_workers
effective_cache_sizeValue used by the query planner to estimate available cache memoryDoes not directly allocate actual memory
Set based on the overall memory size of the database server
maintenance_work_memMaximum memory size for maintenance tasks
(VACUUM, CREATE INDEX, etc.)
Memory is allocated separately per task
If multiple tasks run simultaneously, total memory usage may increase
shared_buffersShared memory size for caching table and index dataToo small: possible performance degradation
Too large: possible system overload or failure
work_memMemory size allocated for query operations such as sorting, hashing, and aggregationMemory is allocated separately per operation
If concurrent queries increase, total memory usage may increase

Connection and process parameters

Parameter nameDescriptionNotes when modifying
max_connectionsMaximum number of client connections allowed simultaneouslyUses system resources per connection
Setting an excessively high value may increase CPU and memory usage and cause system load
max_parallel_workersMaximum number of parallel workers allowed on the serverSetting a large value that does not match server specifications may increase CPU and memory usage and cause system load
max_worker_processesMaximum number of background workers that can run for parallel processing, background tasks, extensions, and similar operationsToo low: features may fail or parallel processing may be limited
Too high: service startup issues may occur due to insufficient memory

Lock and transaction parameters

Parameter nameDescriptionNotes when modifying
max_locks_per_transactionMaximum number of locks that can be acquired per transactionSetting an excessively high value may cause service startup issues due to insufficient memory
max_pred_locks_per_transactionMaximum number of predicate locks that can be acquired per transactionSetting an excessively high value may cause service startup issues due to insufficient memory
max_prepared_transactionsMaximum number of prepared transactions that can be used simultaneouslySetting an excessively high value may cause service startup issues due to insufficient memory

WAL and replication parameters

Parameter nameDescriptionNotes when modifying
wal_keep_sizeMinimum size of WAL files to retainIf replication delay occurs, the Standby server may not receive required WAL files
Set a sufficient value to maintain replication connections

Among the provided parameters, these have recommended settings based on operational policies or are parameters that cannot be set directly.

Parameter nameDescriptionRestrictions and recommendations
application_nameSpecifies the name of the application executing the current sessionIf a change is needed, session-level configuration with the SET command is recommended
client_encodingSets the character encoding between client and serverIf a change is needed, session-level configuration with the SET command is recommended
Only character sets supported by PostgreSQL can be used
- See the official documentation for supported values
DateStyleSets the date and time output formatIf using a format other than the default DateStyle, per-user configuration with ALTER USER ... SET is recommended
lc_messagesSets the language for messages and error messagesBased on locale information provided by the operating system
Values other than locales registered in the system cannot be set
lc_monetaryLocale that determines currency formattingBased on locale information provided by the operating system
Values other than locales registered in the system cannot be set
lc_numericLocale that determines number formattingBased on locale information provided by the operating system
Values other than locales registered in the system cannot be set
lc_timeLocale that determines date and time formattingBased on locale information provided by the operating system
Values other than locales registered in the system cannot be set
log_statement_statsWhether to log query execution statisticsCan be set only when log_parser_stats, log_planner_stats, and log_executor_stats are all disabled (OFF)
log_timezoneTime zone used for log timestampsOnly time zones provided for major countries and regions can be set
tcp_keepalives_countMaximum number of keepalive packets to send before a TCP connection is droppedDetermined by the operating system TCP Keepalive settings
Cannot be modified directly
tcp_keepalives_idleMaximum time in seconds a TCP connection can remain inactiveDetermined by the operating system TCP Keepalive settings
Cannot be modified directly
tcp_keepalives_intervalTCP keepalive packet interval in secondsDetermined by the operating system TCP Keepalive settings
Cannot be modified directly
TimeZoneDefault time zone used by the serverOnly time zones provided for major countries and regions can be set
wal_bufferWAL log buffer sizeValues 0 ~ 3 cannot be set due to database constraints