Fix typos

tablesapce -> tablespace
there -> their

These were introduced in 72d422a52, so no need to backpatch.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index def43a21da2439c0746d16c42aab89cbd80121c5..75dabe9f29f804a78d7513f5c0a05eb8f2e1990e 100644 (file)
--- 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 5bebf99c3978c42a7a70bed4e913da165ecb2e73..150d56afb8fc341b585ef6947bebc02b132aa2ae 100644 (file)
--- 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