There are two methods of managing Fujitsu Enterprise Postgres operations:
Operation management using GUI tools
Operation management using commands
See
Before performing database multiplexing using database multiplexing, refer to "Database Multiplexing Mode" in the Cluster Operation Guide (Database Multiplexing).
Operation management using GUI tools
This involves managing operations using the WebAdmin.
Management using WebAdmin
This removes the requirement for complex environment settings and operational design for backup and recovery that is usually required for running a database. It enables you to easily and reliably monitor the state of the database, create a streaming replication cluster, back up the database, and restore it even if you do not have expert knowledge of databases.
Operation management using commands
You can use commands for configuring and operating the database and managing operations.
Points to consider when choosing an operation method
You cannot combine WebAdmin and server commands to perform the following operations:
Use commands to operate an instance created using WebAdmin.
Use WebAdmin to recover a database backed up using commands.
For instances created with WebAdmin, however, backup can be obtained with the pgx_dmpall command. Also, WebAdmin can perform recovery by using the backup obtained with the pgx_dmpall command.
To compress the backup files, use the pgx_dmpall command in WebAdmin operations as well.
To operate an instance created using the initdb command in WebAdmin, the instance needs to be imported using WebAdmin.
Features used in each phase
The following table lists the features used in each phase for GUI-based operations and command-based operations.
Operation | Operation with the GUI | Operation with commands | |
---|---|---|---|
Setup | Creating an instance | WebAdmin is used. | The configuration file is edited directly using the initdb command. |
Creating a standby instance | WebAdmin is used. WebAdmin performs a base backup of the source instance and creates a standby instance. | A standby instance is created using the pg_basebackup command. | |
Changing the configuration files | WebAdmin is used. | The configuration file is edited directly. | |
Starting and stopping an instance | WebAdmin is used. | The pg_ctl command is used. | |
Creating a database | None. | This is defined using the psql command or the application after specifying the DDL statement. | |
Backing up the database | WebAdmin, or the pgx_dmpall command, is used. | It is recommended that the pgx_dmpall command be used. Recovery to the latest database can be performed. | |
Database recovery | WebAdmin is used. | To use the backup that was performed using the pgx_dmpall command, the pgx_rcvall command is used. | |
Monitoring | Database errors | The status in the WebAdmin window can be checked. | The messages that are output to the database server log are monitored. |
Disk space | The status in the WebAdmin window can be checked. A warning will be displayed if the free space falls below 20%. | This is monitored using the df command of the operating system, for example. | |
Connection status | None. | This can be checked referencing pg_stat_activity of the standard statistics view from psql or the application. |