| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_resetxlog options |
| Date: | 2004-11-07 20:48:56 |
| Message-ID: | 23921.1099860536@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-11-07 20:59:46 | Re: Increasing the length of pg_stat_activity.current_query... |
| Previous Message | Bruce Momjian | 2004-11-07 20:47:23 | Re: cygwin build failure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hansen | 2004-11-07 22:21:50 | calling currval() before nextval() patch adding currval_isset() |
| Previous Message | Bruce Momjian | 2004-11-07 20:47:23 | Re: cygwin build failure |