User command called from the pgx_dmpall command.

The syntax for calling the copy command from the pgx_dmpall command is described below.

If the operation mode is "prepare"

copyCommandName prepare 'pathOfBackupInfoFile' 'pathOfBackupTargetListFile'

If the operation mode is "backup"

copyCommandName backup

If the operation mode is "finalize"

copyCommandName finalize 'pathOfBackupInfoFile'

• Operation mode

  Mode	Description
  prepare	Implements the preparation process for backing up using the copy command. Called before the PostgreSQL backup mode is started.
  backup	Implements the backup process. Called during the PostgreSQL backup mode.
  finalize	Implements the backup completion process. Called after the PostgreSQL backup mode is completed.

• Full path of the backup information file

  Full path of the backup information file of the latest backup, enclosed in single quotation marks. If a backup has not been performed, specify '-'.

• Full path of the backup target list file

  Full path of the file containing the resources to be backed up using the copy command, enclosed in single quotation marks. One of the following is described in each resource name.

  Resource	Description
  Database cluster	pg_data
  Tablespace	Tablespace name

  Example

  To back up the database cluster and the tablespaces dbspace and indexspace using the copy command, the file should contain the following:

  pg_data
  dbspace
  indexspace

  Information

  The encoding of resource names output to the backup target list file by the pgx_dmpall command is the encoding used when this command connects to the database with auto specified for the client_encoding parameter, and is dependent on the locale at the time of command execution.

The number of arguments vary depending on operation mode. The argument of each operation mode is as follows.

Additionally, the access permissions for the backup information file and backup target list file are different depending on the operation mode. The access permissions of each operation mode are as follows.

• The copy command operates with the privileges of the operating system user who executed the pgx_dmpall command. Therefore, grant copy command execution privileges to users who will execute the pgx_dmpall command. Additionally, have the copy command change users as necessary.

• To write to the backup information file, use a method such as redirection from the copy command.

• Because the copy command is called for each mode, implement all processing for each one.

• To copy multiple resources simultaneously, have the copy command copy them in parallel.

• The backup information file and backup target list file cannot be deleted. Additionally, the privileges cannot be changed.

• Standard output and standard error output of the copy command are output to the terminal where the pgx_dmpall command was executed.

• If the copy command becomes unresponsive, the pgx_dmpall command will also become unresponsive. If the copy command is deemed to be unresponsive by the operating system, use an operating system command to forcibly stop it.

• Output the copy command execution trace and the result to a temporary file, so that if it terminates in error, the cause can be investigated at a later time.

• For prepare mode only, it is possible to use the PostgreSQL client application to access the database using the copy command. For all other modes, do not execute Fujitsu Enterprise Postgres commands or PostgreSQL applications.

• Enable the fsync parameter in postgresql.conf, because data on the shared memory buffer needs to have been already written to disk when backup starts.