Re: pg_resetxlog options

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_resetxlog options
Date: 2004-11-17 20:52:48
Message-ID: 419BBA20.4020304@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)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.
>
>
>

Some other time maybe. Meanwhile, this patch ought to make it compile
more cleanly on Windows - not sure why I get errors there but not Linux.

cheers

andrew

Attachment Content-Type Size
resetxlog.patch text/x-patch 610 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2004-11-17 21:07:34 ambiguous column names in subqueries
Previous Message Tom Lane 2004-11-17 19:59:56 Re: Tired of -Wold-style-definition already

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-11-17 21:39:05 Re: pg_resetxlog options
Previous Message Tom Lane 2004-11-17 18:06:46 Re: Small patch for regression tests