| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> | 
|---|---|
| To: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: -X flag in pg_dump | 
| Date: | 2006-01-26 14:02:56 | 
| Message-ID: | 200601261402.k0QE2u607203@candle.pha.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Dennis Bjorklund wrote:
> What use is the -X flag to pg_dump. The code say that if one add a setting 
> "feature" to -X then there should also be a flag "--feature". So we have 
> for example:
> 
>   -X disable-triggers
> 
> and 
> 
>   --disable-triggers
> 
> If all the -X flags come in a long form as well, then what use is the -X
> at all? Why would one want to use -X disable-triggers instead of
> --disable-triggers ?
The issue is that some operating systems do not support long options, so
-X option is really -X and an argument, while --option is a long option.
We have our own getopt.c library so I am unsure we really need have
cases that don't support long options anymore.
-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | William ZHANG | 2006-01-26 14:15:00 | Re: debug_query_string and multiple statements | 
| Previous Message | Ewa Papuga | 2006-01-26 13:47:15 |