Yury Bokhoncovich writes:
> They may silently ignore this option. Nothing has changed comparing
> with original behaviour if the option is not explicitly enabled.
> In fact it is alike --with-recode/locale configure options or target one and
> to make ease a sysadmin life and to save a few tciks of CPU: if I ALWAYS
> set Eurodates by default thru -o'e' option, why not do it at compile time
> rather than run time?
The rules of the game are as follows:
1) If an option possibly can be a run-time option then it should be one
rather than a compile-time option. This allows users of binary packages
to have the same flexibility as users of the source code distribution.
(The --enable-locale option is actually slated for that kind of move
soon.) Having the option in both places is confusing.
2) No compile-time option may replace one behavior by another. This
allows binary packagers to make unbiased decisions about which options to
activate. (Note that --enable-locale does not replace behavior, it simply
adds more.)
What we want to do is integrate the SET DateStyle variable into GUC
somehow, but I'm not entirely happy with the current behavior and have
been unable to agree with Thomas Lockhart on how to do it. But it will
get done eventually.
--
Peter Eisentraut peter_e@gmx.net
