mirror of
https://github.com/pgadmin-org/pgadmin4.git
synced 2025-02-25 18:55:31 -06:00
Added support for viewing Log Based Clusters. #7216
Co-authored-by: Akshay Joshi <akshay.joshi@enterprisedb.com>
This commit is contained in:
BIN
docs/en_US/images/replica_nodes_general.png
Normal file
BIN
docs/en_US/images/replica_nodes_general.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
BIN
docs/en_US/images/replica_nodes_replication.png
Normal file
BIN
docs/en_US/images/replica_nodes_replication.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 73 KiB |
@@ -18,4 +18,5 @@ database, right-click on the *Databases* node, and select *Create Database...*
|
||||
resource_group_dialog
|
||||
role_dialog
|
||||
tablespace_dialog
|
||||
replica_nodes_dialog
|
||||
role_reassign_dialog
|
||||
46
docs/en_US/replica_nodes_dialog.rst
Normal file
46
docs/en_US/replica_nodes_dialog.rst
Normal file
@@ -0,0 +1,46 @@
|
||||
.. _replica_nodes_dialog:
|
||||
|
||||
****************************
|
||||
`Replica Node Dialog`:index:
|
||||
****************************
|
||||
|
||||
Use The *Replica Node* dialog to view a standby instance being replicated
|
||||
using log based streaming replication. Streaming replication allows a standby
|
||||
server to stay more up-to-date than is possible with file-based log shipping.
|
||||
The standby connects to the primary, which streams WAL records to the standby as
|
||||
they're generated, without waiting for the WAL file to be filled.
|
||||
|
||||
The *Replica Node* dialog organizes the information through the following tabs:
|
||||
*General*, *Replication Slot*
|
||||
|
||||
.. image:: images/replica_nodes_general.png
|
||||
:alt: Replica Node dialog general tab
|
||||
:align: center
|
||||
|
||||
* The *PID* field is the process ID of a WAL sender process.
|
||||
* The *Username* field is the name of the user logged into this WAL sender process.
|
||||
* The *App Name* field is the name of the application that is connected to this WAL sender.
|
||||
* The *Client Address* field is the IP address of the client connected to this WAL sender.
|
||||
If this field is null, it indicates that the client is connected via a Unix socket on the server machine.
|
||||
* The *Client Hostname* field is the host name of the connected client, as reported by a reverse DNS lookup
|
||||
of client_addr.This field will only be non-null for IP connections, and only when log_hostname is enabled.
|
||||
* The *Client Port* field is the TCP port number that the client is using for communication with
|
||||
this WAL sender, or -1 if a Unix socket is used.
|
||||
* The *State* field is the current WAL sender state.
|
||||
|
||||
Click the *Replication Slot* tab to continue.
|
||||
|
||||
.. image:: images/replica_nodes_replication.png
|
||||
:alt: Replica Node dialog replication slot tab
|
||||
:align: center
|
||||
|
||||
* The *Slot Name* field is a unique, cluster-wide identifier for the replication slot.
|
||||
* The *Slot Type* field is the slot type - physical or logical
|
||||
* The *Active* field is True if this slot is currently actively being used.
|
||||
|
||||
Other buttons:
|
||||
|
||||
* Click the *Info* button (i) to access online help.
|
||||
* Click the *Save* button to save work.
|
||||
* Click the *Close* button to exit without saving work.
|
||||
* Click the *Reset* button to restore configuration parameters.
|
||||
Reference in New Issue
Block a user