From 94232c909da4e39273efd66fc7c9c4a3fd9ef51a Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Mon, 8 Jun 2015 15:35:43 -0300 Subject: [PATCH] Fix typos tablesapce -> tablespace there -> their These were introduced in 72d422a52, so no need to backpatch. --- doc/src/sgml/backup.sgml | 2 +- src/backend/access/transam/xlog.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index def43a21da2..75dabe9f29f 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -969,7 +969,7 @@ SELECT pg_stop_backup(); It's also worth noting that the pg_start_backup function makes files named backup_label and - tablesapce_map in the database cluster directory, + tablespace_map in the database cluster directory, which are removed by pg_stop_backup. These files will of course be archived as a part of your backup dump file. The backup label file includes the label string you gave to pg_start_backup, diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c index 5bebf99c397..150d56afb8f 100644 --- a/src/backend/access/transam/xlog.c +++ b/src/backend/access/transam/xlog.c @@ -6203,7 +6203,7 @@ StartupXLOG(void) * safest to just remove them always and let them be rebuilt during the * first backend startup. These files needs to be removed from all * directories including pg_tblspc, however the symlinks are created only - * after reading tablesapce_map file in case of archive recovery from + * after reading tablespace_map file in case of archive recovery from * backup, so needs to clear old relcache files here after creating * symlinks. */ @@ -9728,7 +9728,7 @@ XLogFileNameP(TimeLineID tli, XLogSegNo segno) * A non-exclusive backup is used for the streaming base backups (see * src/backend/replication/basebackup.c). The difference to exclusive backups * is that the backup label and tablespace map files are not written to disk. - * Instead, there would-be contents are returned in *labelfile and *tblspcmapfile, + * Instead, their would-be contents are returned in *labelfile and *tblspcmapfile, * and the caller is responsible for including them in the backup archive as * 'backup_label' and 'tablespace_map'. There can be many non-exclusive backups * active at the same time, and they don't conflict with an exclusive backup