pgsql: Our version of getopt_long does not set optarg upon detecting an

From: alvherre(at)postgresql(dot)org (Alvaro Herrera)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Our version of getopt_long does not set optarg upon detecting an
Date: 2006-06-25 04:38:08
Message-ID: 20060625043808.6D9E49FA42B@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/bin/pg_ctl:
pg_ctl.c (r1.53.4.3 -> r1.53.4.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_ctl/pg_ctl.c.diff?r1=1.53.4.3&r2=1.53.4.4)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Meskes 2006-06-25 09:38:40 pgsql: Moved some free() calls that coverity correctly complains about.
Previous Message Alvaro Herrera 2006-06-25 04:38:00 pgsql: Our version of getopt_long does not set optarg upon detecting an