Commit94232c9

committed

Fix typos

tablesapce -> tablespacethere -> theirThese were introduced in72d422a, so no need to backpatch.

1 parent7abc685 commit94232c9Copy full SHA for 94232c9

File tree

-3

lines changed

-3

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -969,7 +969,7 @@ SELECT pg_stop_backup();`
`969`	`969`	`<para>`
`970`	`970`	`It's also worth noting that the <function>pg_start_backup</> function`
`971`	`971`	`makes files named <filename>backup_label</> and`
`972`		`- <filename>tablesapce_map</> in the database cluster directory,`
	`972`	`+ <filename>tablespace_map</> in the database cluster directory,`
`973`	`973`	`which are removed by <function>pg_stop_backup</>. These files will of`
`974`	`974`	`course be archived as a part of your backup dump file. The backup label`
`975`	`975`	`file includes the label string you gave to <function>pg_start_backup</>,`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -6203,7 +6203,7 @@ StartupXLOG(void)`
`6203`	`6203`	`* safest to just remove them always and let them be rebuilt during the`
`6204`	`6204`	`* first backend startup. These files needs to be removed from all`
`6205`	`6205`	`* directories including pg_tblspc, however the symlinks are created only`
`6206`		`- * after readingtablesapce_map file in case of archive recovery from`
	`6206`	`+ * after readingtablespace_map file in case of archive recovery from`
`6207`	`6207`	`* backup, so needs to clear old relcache files here after creating`
`6208`	`6208`	`* symlinks.`
`6209`	`6209`	`*/`
`@@ -9728,7 +9728,7 @@ XLogFileNameP(TimeLineID tli, XLogSegNo segno)`
`9728`	`9728`	`* A non-exclusive backup is used for the streaming base backups (see`
`9729`	`9729`	`* src/backend/replication/basebackup.c). The difference to exclusive backups`
`9730`	`9730`	`* is that the backup label and tablespace map files are not written to disk.`
`9731`		`- * Instead,there would-be contents are returned in labelfile and tblspcmapfile,`
	`9731`	`+ * Instead,their would-be contents are returned in labelfile and tblspcmapfile,`
`9732`	`9732`	`* and the caller is responsible for including them in the backup archive as`
`9733`	`9733`	`* 'backup_label' and 'tablespace_map'. There can be many non-exclusive backups`
`9734`	`9734`	`* active at the same time, and they don't conflict with an exclusive backup`

Comments

(0)