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

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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.



Attachment: resetxlog.patch
Description: text/x-patch (610 bytes)

In response to


pgsql-hackers by date

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

pgsql-patches by date

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

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