Re: pg_resetxlog options - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_resetxlog options
Date
Msg-id 23921.1099860536@sss.pgh.pa.us
Whole thread Raw
In response to pg_resetxlog options  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_resetxlog options
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Why does pg_resetxlog seem top be the only one of our programs that has 
> no long form options (or at least the only one that calls getopt rather 
> than getopt_long)? Should we make it consistent with everything else?

I think just laziness on my part when I first wrote it --- it only had
one or two options anyway, and didn't seem to need long options.  But if
converting to getopt_long is the easy way to avoid a porting problem,
do it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: cygwin build failure
Next
From: Greg Stark
Date:
Subject: Re: Increasing the length of pg_stat_activity.current_query...