Our version of getopt_long does not set optarg upon detecting an error, as

opposed to what other versions apparently do, so it's not safe to print an
error message.  Besides, getopt_long itself already did, so it's redundant
anyway.
This commit is contained in:
Alvaro Herrera 2006-06-25 04:38:00 +00:00
parent 1c718dd8bf
commit 15af8b771b

View File

@ -4,7 +4,7 @@
* *
* Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group * Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group
* *
* $PostgreSQL: pgsql/src/bin/pg_ctl/pg_ctl.c,v 1.61.2.2 2006/01/14 16:16:08 petere Exp $ * $PostgreSQL: pgsql/src/bin/pg_ctl/pg_ctl.c,v 1.61.2.3 2006/06/25 04:38:00 alvherre Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -1418,7 +1418,7 @@ main(int argc, char **argv)
wait_set = true; wait_set = true;
break; break;
default: default:
write_stderr(_("%s: invalid option %s\n"), progname, optarg); /* getopt_long already issued a suitable error message */
do_advice(); do_advice();
exit(1); exit(1);
} }