database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

Fix typos

Browse Source 
tablesapce -> tablespace
there -> their

These were introduced in 72d422a52, so no need to backpatch.
This commit is contained in:
Alvaro Herrera 2015-06-08 15:35:43 -03:00
parent 7abc685974
commit 94232c909d
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/backup.sgml
View File

@ -969,7 +969,7 @@ SELECT pg_stop_backup();
<para>
It's also worth noting that the <function>pg_start_backup</> function
makes files named <filename>backup_label</> and
<filename>tablesapce_map</> in the database cluster directory,
<filename>tablespace_map</> in the database cluster directory,
which are removed by <function>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 <function>pg_start_backup</>,

4
src/backend/access/transam/xlog.c
View File

@ -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