PG_STAT_REPLICATION

startup: The thread is being started.
catchup: The thread is establishing a connection between the standby server and the primary server.
streaming: The thread has established a connection between the standby server and the primary server and is replicating data streams.
backup: The thread is sending a backup.
stopping: The thread is being stopped.

PG_STAT_REPLICATION displays information about the log synchronization thread, such as the locations where the sender sends logs and where the receiver receives logs.

**Table 1** PG_STAT_REPLICATION columns
Name	Type	Description
pid	bigint	Process ID of the thread
usesysid	oid	User system ID
usename	name	Username
application_name	text	Program name
client_addr	inet	Client address
client_hostname	text	Client name
client_port	integer	Port of the client
backend_start	timestamp with time zone	Start time of the program
state	text	State of the log synchronization thread: startup: The thread is being started. catchup: The thread is establishing a connection between the standby server and the primary server. streaming: The thread has established a connection between the standby server and the primary server and is replicating data streams. backup: The thread is sending a backup. stopping: The thread is being stopped.
sender_sent_location	text	Location where the sender sends logs
receiver_write_location	text	Location where the receiver writes logs
receiver_flush_location	text	Location where the receive end flushes logs
receiver_replay_location	text	Location where the receive end replays logs
sync_priority	integer	Priority of synchronous duplication (0 indicates asynchronization.)
sync_state	text	Synchronization state async: asynchronous replication. sync: synchronous replication. potential: The standby server is asynchronous currently, but if a current synchronization server fails, the standby server becomes synchronous. Qurom: switches between the synchronous and asynchronous states to ensure that there are more than a certain number of synchronous standby servers. Generally, the number of synchronous standby servers is (n+1)/2-1, where n indicates the total number of copies. Whether the standby server is synchronous depends on whether logs are received first. For details, see the description of the synchronous_standby_names parameter.