The procedure for stopping database multiplexing mode and changing to single server mode is explained below.
Determine the server for which the instance is to be stopped, and switch this server
Determine the server that is to be excluded as the database multiplexing mode target, and for which the instance is to be stopped.
If the server for which the instance is to be stopped is the primary server, execute the mc_ctl command in the switch mode to switch the standby server to the primary server.
The standby server after the switch is complete will be the server for which the instance is to be stopped.
If the server for which the instance is to be stopped is the standby server, there is no need to perform the switch operation.
Example)
$ mc_ctl switch -M /mcdir/inst1
Stop Mirroring Controller and the instance, and delete the file resources
On the server that was determined in step 1, execute the mc_ctl command in stop mode to stop Mirroring Controller and the instance.
Example)
$ mc_ctl stop -M /mcdir/inst1
Then, delete the following file resources:
Data storage destination directory
Mirroring Controller management directory
Example)
$ rm -rf /database/inst1 $ rm -rf /mcdir/inst1
See
Refer to "Security-Related Notes" in the Operation Guide for details on deleting the data securely.
Stop Mirroring Controller on the primary server
Execute the mc_ctl command in stop mode on the primary server.
Example)
$ mc_ctl stop -M /mcdir/inst1
Delete the database multiplexing mode settings that were configured for the primary server instance.
Each parameter and resource is shown in the table below.
Database multiplexing parameters in postgresql.conf and recovery.conf
Primary server settings
File | Parameter | Action |
|---|---|---|
postgresql.conf | wal_level | Delete the "hot_standby" value that was specified. |
max_wal_senders | Revert the value to the one set before database multiplexing mode was set. | |
synchronous_standby_names | Delete. | |
replication_timeout | ||
listen_addresses | Revert the value to the one set before database multiplexing mode was set. | |
max_connections |
Standby server settings
File | Parameter | Action |
|---|---|---|
postgresql.conf | synchronous_standby_names | Delete. |
hot_standby | ||
wal_receiver_status_interval | ||
recovery.conf | standby_mode | Delete. Note that this file is created automatically when the mc_ctl command is executed in setup mode. |
primary_conninfo |
Mirroring Controller management directory
Additionally, if the backup operation was performed, delete the following resources:
Mirroring Controller management directory backup data obtained in database multiplexing mode
Instance backup data obtained in database multiplexing mode
After these actions are performed, ensure that the backup data is collected when starting the single operation.
Note
If using together with WebAdmin
Instances that run in database multiplexing mode cannot be accessed from WebAdmin, even if the database multiplexing mode is stopped and operations are changed to single server mode. Using WebAdmin, create a new instance.
Refer to "Setup" in the Installation and Setup Guide for Server for information on creating instances.
See
Refer to "Security-Related Notes" in the Operation Guide for details on deleting the data securely.
Refer to "6.11 Backup Operation" for details on the backup operation.
Refer to "Appendix B Parameters" for details on the postgresql.conf file parameters.
