From 323bcca5249c707b68d9f6d921d86fd750bcf33e Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 14 May 2024 21:16:20 +0200 Subject: Merging upstream version 16.3. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/backup-file.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/backup-file.html') diff --git a/doc/src/sgml/html/backup-file.html b/doc/src/sgml/html/backup-file.html index 92710b2..b57ca61 100644 --- a/doc/src/sgml/html/backup-file.html +++ b/doc/src/sgml/html/backup-file.html @@ -1,5 +1,5 @@ -26.2. File System Level Backup
26.2. File System Level Backup
Prev UpChapter 26. Backup and RestoreHome Next

26.2. File System Level Backup #

+26.2. File System Level Backup

26.2. File System Level Backup
Prev UpChapter 26. Backup and RestoreHome Next

26.2. File System Level Backup #

An alternative backup strategy is to directly copy the files that PostgreSQL uses to store the data in the database; Section 19.2 explains where these files @@ -88,4 +88,4 @@ tar -cf backup.tar /usr/local/pgsql/data than an SQL dump. (pg_dump does not need to dump the contents of indexes for example, just the commands to recreate them.) However, taking a file system backup might be faster. -

Prev Up Next
26.1. SQL Dump Home 26.3. Continuous Archiving and Point-in-Time Recovery (PITR)
\ No newline at end of file +

Prev Up Next
26.1. SQL Dump Home 26.3. Continuous Archiving and Point-in-Time Recovery (PITR)
\ No newline at end of file -- cgit v1.2.3