For the complete documentation index, see llms.txt. This page is also available as Markdown.

PostgreSQL 11

This page describes the Optimization Pack for the component type PostgreSQL 11.

Metrics

Concurrency

Parameter
Unit
Description

pg_connections

connections

The number of connections in the db.

Transactions

Parameter
Unit
Description

pg_start_time

seconds

The total amount time spent by postresql to boot up.

pg_commits

commits/s

The number of transactions committed per second.

pg_rollbacks

rollbacks/s

The number of transactions rollbacked per second.

Checkpoints

Parameter
Unit
Description

pg_checkpoint_executed

checkpoints/s

The total number of checkpoint operations executed by postgresql.

Disks

Metric
Unit
Description

pg_disk_used

bytes

The amount of disk space used by postgresql.

pg_blocks_read

blocks/s

The number of blocks read per second by postgresql.

pg_blocks_cache_hit

blocks/s

Number of blocks found in the buffer cache.

pg_backend_fsync_count

syncs

The total number of times postgresql executed a sync of data to disk.

Parameters

Concurrency

Parameter
Type
Unit
Default value
Domain
Restart
Description

pg_effective_io_concurrency

integer

iops

1

01000

no

The number of simultaneous requests that can be handled efficiently by the disk subsystem.

Background Writer

Parameter
Type
Unit
Default value
Domain
Restart
Description

pg_bgwriter_delay

integer

milliseconds

200

1010000

no

The delay between activity rounds for the background writer.

pg_bgwriter_lru_maxpages

integer

buffers

100

01073741823

no

The maximum number of LRU pages to flush per round by the background writer.

Checkpoints

Parameter
Type
Unit
Default value
Domain
Restart
Description

pg_checkpoint_completion_target

real

0.5

0.01.0

no

The time spent flushing dirty buffers during checkpoint, as fraction of checkpoint interval.

Disks

Parameter
Type
Unit
Default value
Restart
Description

pg_effective_cache_size

integer

kilobytes

524288

12147483647

no

The planner's assumption about the effective size of the disk cache available to a single query. A higher value makes it more likely index scans will be used, a lower value makes it more likely sequential scans will be used.

Last updated

Was this helpful?