aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2015-06-08 15:35:43 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2015-06-08 15:37:42 -0300
commit94232c909da4e39273efd66fc7c9c4a3fd9ef51a (patch)
tree0dd751bd68d5eaf4c02cbefbe9b06233441bdab0 /src/backend/access/transam/xlog.c
parent7abc68597436da1475b4d9b08f4fa9f3c5ed6185 (diff)
downloadpostgresql-94232c909da4e39273efd66fc7c9c4a3fd9ef51a.tar.gz
postgresql-94232c909da4e39273efd66fc7c9c4a3fd9ef51a.zip
Fix typos
tablesapce -> tablespace there -> their These were introduced in 72d422a52, so no need to backpatch.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
-rw-r--r--src/backend/access/transam/xlog.c4
1 files changed, 2 insertions, 2 deletions
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