diff options
| author | Robert Haas <rhaas@postgresql.org> | 2016-10-20 11:24:37 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2016-10-20 11:32:18 -0400 |
| commit | f82ec32ac30ae7e3ec7c84067192535b2ff8ec0e (patch) | |
| tree | 929d4709a42149a4bbde12edad16183a96bcef6a /src/backend/access/transam/xlogfuncs.c | |
| parent | ec7db2b483e0ff247ed41612cdb5716022401fe6 (diff) | |
| download | postgresql-f82ec32ac30ae7e3ec7c84067192535b2ff8ec0e.tar.gz postgresql-f82ec32ac30ae7e3ec7c84067192535b2ff8ec0e.zip | |
Rename "pg_xlog" directory to "pg_wal".
"xlog" is not a particularly clear abbreviation for "write-ahead log",
and it sometimes confuses users into believe that the contents of the
"pg_xlog" directory are not critical data, leading to unpleasant
consequences. So, rename the directory to "pg_wal".
This patch modifies pg_upgrade and pg_basebackup to understand both
the old and new directory layouts; the former is necessary given the
purpose of the tool, while the latter merely avoids an unnecessary
backward-compatibility break.
We may wish to consider renaming other programs, switches, and
functions which still use the old "xlog" naming to also refer to
"wal". However, that's still under discussion, so let's do just this
much for now.
Discussion: CAB7nPqTeC-8+zux8_-4ZD46V7YPwooeFxgndfsq5Rg8ibLVm1A@mail.gmail.com
Michael Paquier
Diffstat (limited to 'src/backend/access/transam/xlogfuncs.c')
| -rw-r--r-- | src/backend/access/transam/xlogfuncs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/transam/xlogfuncs.c b/src/backend/access/transam/xlogfuncs.c index 33383b4dccb..01cbd90f40a 100644 --- a/src/backend/access/transam/xlogfuncs.c +++ b/src/backend/access/transam/xlogfuncs.c @@ -128,7 +128,7 @@ pg_start_backup(PG_FUNCTION_ARGS) * pg_stop_backup: finish taking an on-line backup dump * * We write an end-of-backup WAL record, and remove the backup label file - * created by pg_start_backup, creating a backup history file in pg_xlog + * created by pg_start_backup, creating a backup history file in pg_wal * instead (whence it will immediately be archived). The backup history file * contains the same info found in the label file, plus the backup-end time * and WAL location. Before 9.0, the backup-end time was read from the backup |