From 94232c909da4e39273efd66fc7c9c4a3fd9ef51a Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Mon, 8 Jun 2015 15:35:43 -0300 Subject: Fix typos tablesapce -> tablespace there -> their These were introduced in 72d422a52, so no need to backpatch. --- src/backend/access/transam/xlog.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/access/transam/xlog.c') 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 -- cgit v1.2.3