PG_STAT_REPLICATION
PG_STAT_REPLICATION displays information about log synchronization status, such as the locations of the sender sending logs and the receiver receiving logs.
| 
        Column  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        pid  | 
      
        Bigint  | 
      
        PID 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  | 
      
        Client port number.  | 
     
| 
        backend_start  | 
      
        Timestamp with time zone  | 
      
        Program start time.  | 
     
| 
        state  | 
      
        Text  | 
      
        Log replication state (catch-up or consistent streaming).  | 
     
| 
        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 receiver flushes logs.  | 
     
| 
        receiver_replay_location  | 
      
        Text  | 
      
        Location where the receiver replays logs.  | 
     
| 
        sync_priority  | 
      
        Integer  | 
      
        Priority of synchronous duplication (0 indicates asynchronization).  | 
     
| 
        sync_state  | 
      
        Text  | 
      
        Synchronization state (asynchronous duplication, synchronous duplication, or potential synchronization).  | 
     
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.