will propagate to the standby. pg_cancel_backend() and pg_terminate_backend() will work on user backends, but not the Startup process, which performs recovery. pg_stat_activity does not show an entry for the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction man- aged by the Startup process that owns Chapter 27. Monitoring Database Activity Column Type Description numbackends integer Number of backends currently connected to this database. This is the only column in this view that returns a value

will propagate to the standby. pg_cancel_backend() and pg_terminate_backend() will work on user backends, but not the Startup process, which performs recovery. pg_stat_activity does not show an entry for the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction managed by the Startup process that owns all Chapter 27. Monitoring Database Activity Column Type Description numbackends integer Number of backends currently connected to this database. This is the only column in this view that returns a value

Chapter 25. High Availability, Load Balancing, and Replication pg_cancel_backend() will work on user backends, but not the Startup process, which performs recovery. pg_stat_activity does not show an entry for the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction managed by the Startup process that owns all change these parameters with SET.) The statistics collector transmits the collected information to backends (including autovacuum) through temporary files. These files are stored in the pg_stat_tmp subdirectory

and eventually those changes will propagate to the standby. pg_cancel_backend() will work on user backends, but not the Startup process, which performs recov- ery. pg_stat_activity does not show an entry the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction man- aged by the Startup process that owns change these parameters with SET.) The statistics collector transmits the collected information to backends (including autovacuum) through temporary files. These files are stored in the pg_stat_tmp subdirectory

will propagate to the standby. pg_cancel_backend() and pg_terminate_backend() will work on user backends, but not the Startup process, which performs recovery. pg_stat_activity does not show an entry for the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction man- aged by the Startup process that owns Chapter 27. Monitoring Database Activity Column Type Description numbackends integer Number of backends currently connected to this database. This is the only column in this view that returns a value

will propagate to the standby. pg_cancel_backend() and pg_terminate_backend() will work on user backends, but not the Startup process, which performs recovery. pg_stat_activity does not show an entry for the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction managed by the Startup process that owns all Chapter 27. Monitoring Database Activity Column Type Description numbackends integer Number of backends currently connected to this database. This is the only column in this view that returns a value

and eventually those changes will propagate to the standby. pg_cancel_backend() will work on user backends, but not the Startup process, which performs recov- ery. pg_stat_activity does not show an entry the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction man- aged by the Startup process that owns are allowed to change these parameters with SET.) The statistics collector communicates with the backends needing information (including autovacuum) through temporary files. These files are stored in the

and eventually those changes will propagate to the standby. pg_cancel_backend() will work on user backends, but not the Startup process, which performs recovery. pg_stat_activity does not show an entry for the primary and issue commands to resolve transactions there. pg_locks will show locks held by backends, as normal. pg_locks also shows a virtual transaction managed by the Startup process that owns all are allowed to change these parameters with SET.) The statistics collector communicates with the backends needing information (including autovac- uum) through temporary files. These files are stored in

many buffers. Also includes statistics about the shared buffer pool, including buffers written by backends (that is, not by the background writer) and total buffers allocated. pg_stat_database One row per bigint The number of times the background writer has started checkpoints based on requests from backends because the checkpoint_segments has been exceeded or because the CHECKPOINT command has been issued bgwriter_lru_maxpages parameter pg_stat_get_buf_written_backend() bigint The number of buffers written by backends because they needed to allocate a new buffer pg_stat_get_buf_alloc() bigint The total number of

many buffers. Also includes statistics about the shared buffer pool, including buffers written by backends (that is, not by the background writer) and total buffers allocated. pg_stat_database One row per bigint The number of times the background writer has started checkpoints based on requests from backends because the checkpoint_segments has been exceeded or because the CHECKPOINT command has been issued bgwriter_lru_maxpages parameter pg_stat_get_buf_written_backend() bigint The number of buffers written by backends because they needed to allocate a new buffer pg_stat_get_buf_alloc() bigint The total number of