listen_addresses

TCP/IP addresses on which the server listens for connections from client applications

*

port

TCP port the server listens on

5432

max_connections

Maximum number of concurrent connections to the database server

100

shared_buffers

Amount of memory the database server uses for shared memory buffer. A reasonable starting value is 25% of the memory in your system

2048 MB

max_worker_processes

Maximum number of background processes that the system can support

23

max_parallel_workers

Maximum number of workers that the system can support for parallel operations

4

max_parallel_workers_per_gather

Maximum number of workers that can be started by a single Gather or Gather Merge node

2

max_parallel_maintenance_workers

Maximum number of parallel workers that can be started by a single utility command

2

effective_cache_size

Sets the ADPG query planner’s assumption about the effective size of the disk cache available to a single query. This is factored into estimates of the cost of using an index. The higher this value, the more likely the index scan will be applied. The lower this value, the more likely the sequential scan will be selected

6144 MB

maintenance_work_mem

Memory limit for maintenance operations. Increasing the value for this parameter can improve the performance of operations for cleaning and restoring the database from a copy

1024 MB

work_mem

Non-shared memory limit used for internal operations when the server executes queries (for example, queries to temporary tables) before temporary files on the disk are used. This limit acts as simple resource control, preventing the host from going into swapping due to overallocation. Since the allocated memory is non-shared memory, large and complex requests can exceed the specified limit

5242 kB

min_wal_size

Until WAL disk usage stays below the min_wal_size value, old WAL files are recycled for future use at a checkpoint, rather than removed. This ensures that enough WAL space is reserved to handle spikes in WAL usage, for example, when running large batch jobs

1024 MB

max_wal_size

Memory limit to which the log size can grow between automatic checkpoints. Increasing this setting may increase the recovery time after a failure. The specified limit can be exceeded automatically with a high load on ADPG

4096 MB

wal_keep_size

Specifies the minimum size of segments retained in the pg_wal directory, in case a standby server needs to fetch them for streaming replication. If a standby server connected to a sending server falls behind by more than wal_keep_size MB, the sending server might remove a WAL segment still needed by the standby. In this case, the replication connection is terminated. Downstream connections also fail as a result. If WAL archiving is enabled, the standby server can fetch the segment from archive and recover. The wal_keep_size parameter sets only the minimum size of segments retained in pg_wal. The system might need to retain more segments for WAL archival or to recover from a checkpoint. If wal_keep_size is set to 0, the system does not keep any extra segments for standby purposes, so the number of old WAL segments available to standby servers depends on the location of the previous checkpoint and status of WAL archiving

0 MB

huge_pages

try

superuser_reserved_connections

Number of connection "slots" that are reserved for PostgreSQL superuser connections

3

timescaledb.max_background_workers

Maximum number of background worker processes allocated to TimescaleDB

16

wal_buffers

Amount of shared memory used for WAL data that has not yet been written to disk

16 MB

default_statistics_target

Default statistics target for table columns without a column-specific target set via ALTER TABLE…​SET STATISTICS

100

random_page_cost

Planner’s estimate of the cost of a non-sequentially-fetched disk page

1.1

checkpoint_completion_target

Target time of checkpoint completion as a fraction of total time between checkpoints

0.9

max_locks_per_transaction

The shared lock table tracks locks on max_locks_per_transaction * (max_connections + max_prepared_transactions) objects (for example, tables). Hence, no more than this number of distinct objects can be locked at any one time. This parameter controls the average number of object locks allocated for each transaction. Individual transactions can lock more objects as long as the locks of all transactions fit in the lock table

128

autovacuum_max_workers

Maximum number of autovacuum processes (excluding the autovacuum launcher) that are allowed to run at the same time

10

autovacuum_naptime(seconds)

Minimum delay between autovacuum runs on any given database. In each round, the autovacuum daemon examines the database and executes the VACUUM and ANALYZE commands if it is needed for tables in that database

10

default_toast_compression

Default TOAST compression method for values of a compressible column. Possible values: lz4, pglz

lz4

effective_io_concurrency

Number of concurrent disk I/O operations that can be executed simultaneously. Raising this value will increase the number of I/O operations that a PostgreSQL session attempts to initiate in parallel

256

jit

Specifies whether PostgreSQL may use JIT compilation, if it is available

off

logging_collector

Enables the logging collector — a background process that captures log messages sent to stderr and redirects them into log files

Enabled

log_directory

Directory that contains log files. It can be specified as an absolute path, or relative to the ADPG cluster data directory

log (the absolute path is /pg_data1/adpg14/log)

log_filename

Log file name pattern. A value can include strftime %-escapes to define time-varying file names. If you specify a file name pattern without escapes, use a log rotation utility to save disk space

postgresql-%a.log

log_rotation_age

Maximum period of time to use a log file, after which a new log file is created. If this value is specified without units, it is taken as minutes. Set log_rotation_age to 0 to disable time-based log file creation

1d

log_rotation_size

Maximum size of a log file. After a log file reaches the specified size, a new log file is created. If the value is set without units, it is taken as kilobytes. Set log_rotation_size to 0 to disable size-based log file creation

0

log_min_messages

Minimum severity level of messages to be written to a log file. Possible values are debug5, debug4, debug3, debug2, debug1, info, notice, warning, error, log, fatal, and panic (see the Severity levels table). Messages with the specified severity or higher are included in the log file. For example, if you set log_min_messages to warning, the log file will include the warning, error, log, fatal, and panic messages

warning

log_min_error_statement

Specifies which SQL statements that cause errors are logged. Possible values are debug5, debug4, debug3, debug2, debug1, info, notice, warning, error, log, fatal, and panic (see the Severity levels table). The log file includes SQL statements for messages of the specified severity or higher. To disable error statement logging, set log_min_error_statement to panic

error

Enable SSL

Enables SSL encryption of incoming traffic for the ADPG service

Disabled

Certificate file

Path to the server SSL certificate file

/etc/adpg16/server.crt

Private key file

Path to the file with the private key of the server SSL certificate

/etc/adpg16/server.key

Certificate authority file

Path to the CA certificate file

/etc/adpg16/ca.crt