You can set up the PostgreSQL Recovery Kit through the use of the LKCLI (Command Line Interface).
Creating/Extending/Configuring the PostgreSQL resource from the Command Line
create pgsql
EXAMPLE: #lkcli resource create pgsql --tag <tag> --datadir <data directory> --port <port> --socket <socket> --dbuser <user name> --logfile <full path to log> --switchback <switchback type> --exepath <directory where exe is located> --clientexe <path to psql> --adminexe <path to pg_ctl>
| Option | Default | Description |
|---|---|---|
| --datadir <str> | Absolute path of the directory where the database data is located. | |
| --port <num> | Port number used by PostgreSQL. | |
| --socket <str> | The path of the socket used by PostgreSQL. | |
| --dbuser <str> | Username used by PostgreSQL. | |
| --logfile <str> | Absolute path where the logs are output. | |
| [--exepath <str>] | /usr/bin | Absolute path of the directory where the executable is located. |
| [--clientexe <str>] | <exepath>/psql | Absolute path of the executable “psql”. |
| [--adminexe <str>] | <exepath>/pg_ctl | Absolute path of the executable “pg_ctl”. |
extend pgsql
EXAMPLE: #lkcli resource extend pgsql --tag <tag> --dest <backup node> --switchback <switchback type> --template_prioity <priority> --target_priority <prority> --exepath <directory where exe is located>
| Option | Default | Description |
|---|---|---|
| [--exepath <str>] | Source system exepath. | Absolute path of the directory where the executable file is located on the node to which the resource is extended. If not specified, the setting of the extension origin is inherited. |
config pgsql
EXAMPLE: #lkcli resource config pgsql --tag <tag> --dbuser <user name>
| Option | Default | Description |
|---|---|---|
| [--dbuser <str>] | None | Username used by PostgreSQL. |
Post your comment on this topic.