This section describes how to operate Fujitsu Enterprise Postgres.
There are two methods of managing Fujitsu Enterprise Postgres operations.
Simple operation management using a WebAdmin (web-based GUI tool)
Suitable when using frequently used basic settings and operations for operation management.
This method allows you to perform simple daily tasks such as starting the system before beginning business, and stopping the system when business is over, using an intuitive operation.
Advanced operation management using server commands
Operations that use Fujitsu Enterprise Postgres or PostgreSQL server commands or server applications.
When operating in a system that is automated by operation management middleware (Systemwalker Centric Manager, for example), this method allows you to use more detailed settings and operations and perform higher level operation management.
Refer to Reference and the PostgreSQL Documentation for information on server commands and server applications.
Select one that suits your purposes.
How WebAdmin and Server Commands Work
Here are the differences between using WebAdmin and server commands:
Operation | Operation with the WebAdmin | Operation with commands | |
|---|---|---|---|
Setup | Creating an instance | The server machine capacity, and the optimum parameter for operations using WebAdmin, are set automatically. Instances that you create and manage in WebAdmin are registered in the WebAdmin administrative information, so you must delete the instance from WebAdmin. | The configuration file is edited directly using the initdb command. |
Creating a standby instance | 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 | You can change the values in the configuration file on the WebAdmin screen. | The configuration file is edited directly. | |
Starting and stopping an instance | You can start and stop with one click from the WebAdmin screen. | The pg_ctl command is used. | |
Creating a database | This is defined using pgAdmin of the GUI tool, or 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 cannot be used interchangeably with operation using server commands or server applications. If used, WebAdmin will not be able to properly manage the instance. If you are backing up by using the copy command with the pgx_dmpall command, select the command operation method. | It is recommended that the pgx_dmpall command be used. Recovery to the latest database can be performed. | |
Database recovery | You can recover using a backup taken with WebAdmin or the pgx_dmpall command. | 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. (*1) | The messages that are output to the database server log are monitored (*1) |
Disk space | The status in the WebAdmin window can be checked. A warning will be displayed if the free space falls below 20%. (*1) | This is monitored using the df command of the operating system, for example. (*1) | |
Connection status | This can be checked using pgAdmin of the GUI tool, or referencing pg_stat_activity of the standard statistics view from psql or the application. | ||
*1: This can be used together with system log monitoring using operations management middleware (Systemwalker Centric Manager, for example).
See
Refer to "Periodic Operations" and "Actions when an Error Occurs" in the Operation Guide for information on monitoring and database recovery.
