Skip site navigation (1) Skip section navigation (2)

pgsql: Remove optreset from src/port/ implementations of getopt andget

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove optreset from src/port/ implementations of getopt andget
Date: 2010-12-16 21:23:25
Message-ID: E1PTLIL-0003nM-Ov@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Remove optreset from src/port/ implementations of getopt and getopt_long.

We don't actually need optreset, because we can easily fix the code to
ensure that it's cleanly restartable after having completed a scan over the
argv array; which is the only case we need to restart in.  Getting rid of
it avoids a class of interactions with the system libraries and allows
reversion of my change of yesterday in postmaster.c and postgres.c.

Back-patch to 8.4.  Before that the getopt code was a bit different anyway.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=61b53695fbbedb7fa9d394e71bf2affdc494e6b0

Modified Files
--------------
src/backend/postmaster/postmaster.c |    5 ++---
src/backend/tcop/postgres.c         |    5 ++---
src/include/getopt_long.h           |    1 -
src/port/getopt.c                   |   20 +++++++++++---------
src/port/getopt_long.c              |   20 +++++++++++---------
5 files changed, 26 insertions(+), 25 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-12-16 22:58:11
Subject: pgsql: Improve comments around startup_hacks() code.
Previous:From: Alvaro HerreraDate: 2010-12-16 20:16:58
Subject: Re: pgsql: Fix inconsequential FILE pointer leakage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group