If the target directory is specified as - (dash), the tar contents will be written to standard output, suitable for piping to (for example) gzip. The main data directory's contents will be written to a file named base.tar, and each other tablespace will be written to a separate tar file named after that tablespace's OID. Write the output as tar files in the target directory. (See -tablespace-mapping to change that.) If the cluster contains additional tablespaces, the main data directory will be placed in the target directory, but all other tablespaces will be placed in the same absolute path as they have on the source server. When the cluster has no additional tablespaces, the whole database will be placed in the target directory. Write the output as plain files, with the same layout as the source server's data directory and tablespaces. Note that there are some limitations in taking a backup from a standby: You will also need to enable full_page_writes on the primary. To take a backup from a standby, set up the standby so that it can accept replication connections (that is, set max_wal_senders and hot_standby, and configure its pg_hba.conf appropriately). Pg_basebackup can make a base backup from not only a primary server but also a standby. There can be multiple pg_basebackups running at the same time, but it is usually better from a performance point of view to take only one backup, and copy the result.
Aws postgresql backup plus#
The server must also be configured with max_wal_senders set high enough to provide at least one walsender for the backup plus one for WAL streaming (if used). The connection must be made with a user ID that has REPLICATION permissions (see Section 22.2) or is a superuser, and pg_hba.conf must permit the replication connection. The backup is made over a regular PostgreSQL connection that uses the replication protocol. For selective backups, another tool such as pg_dump must be used. Backups are always taken of the entire database cluster it is not possible to back up individual databases or database objects. Pg_basebackup makes an exact copy of the database cluster's files, while making sure the server is put into and out of backup mode automatically. The backup is taken without affecting other clients of the database, and can be used both for point-in-time recovery (see Section 26.3) and as the starting point for a log-shipping or streaming-replication standby server (see Section 27.2). Pg_basebackup is used to take a base backup of a running PostgreSQL database cluster.
0 kommentar(er)
