aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2016-07-14 15:39:01 +0200
committerMagnus Hagander <magnus@hagander.net>2016-07-14 15:39:01 +0200
commit00e0b67a584b51aac12e4279a31fa5a1130fe05f (patch)
treec94c1a58397446c94eb8edf69707045a56ee418d
parent56a997413391337f7fb9926144d6b6fa831b9d22 (diff)
downloadpostgresql-00e0b67a584b51aac12e4279a31fa5a1130fe05f.tar.gz
postgresql-00e0b67a584b51aac12e4279a31fa5a1130fe05f.zip
Remove reference to range mode in pg_xlogdump error
pg_xlogdump doesn't have any other mode, so it's just confusing to include this in the error message as it indicates there might be another mode.
-rw-r--r--src/bin/pg_xlogdump/pg_xlogdump.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/pg_xlogdump/pg_xlogdump.c b/src/bin/pg_xlogdump/pg_xlogdump.c
index f24dcabb5b9..02575eb1c57 100644
--- a/src/bin/pg_xlogdump/pg_xlogdump.c
+++ b/src/bin/pg_xlogdump/pg_xlogdump.c
@@ -949,7 +949,7 @@ main(int argc, char **argv)
/* we don't know what to print */
if (XLogRecPtrIsInvalid(private.startptr))
{
- fprintf(stderr, "%s: no start log position given in range mode.\n", progname);
+ fprintf(stderr, "%s: no start log position given.\n", progname);
goto bad_argument;
}