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

Re: Eurodates by default

From: Yury Bokhoncovich <byg(at)center-f1(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Eurodates by default
Date: 2002-03-19 17:02:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches

On Tue, 19 Mar 2002, Tom Lane wrote:

> Yury Bokhoncovich <byg(at)center-f1(dot)ru> writes:
> > The patch adds a configure option which enables using eurodates in PgSQL
> > by default (i.e. as if -e option of backend was given).
> > The patch allows to get rid unconvenient -o'e' option for postmaster.
> This strikes me as *entirely* the wrong approach.  A configure option
> is very unwieldy (what of people who want to use RPM packages?).

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?

> Instead of wiring in the behavior at configure time, why not set up
> a GUC variable?

There is no such variable. Yes, I could try to fix it but I'm not sure I

Initially, I wanted to add -e option directly to postmaster but after some
speculation I discard this idea for reason similar to your "wrong

WBR, Yury Bokhoncovich, Senior System Administrator, NOC of F1 Group.
Phone: +7 (3832) 106228, ext.140, E-mail: byg(at)center-f1(dot)ru(dot)
Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.

In response to


pgsql-patches by date

Next:From: Peter EisentrautDate: 2002-03-19 17:21:26
Subject: Re: [HACKERS] Fixes gram.y
Previous:From: Tom LaneDate: 2002-03-19 16:59:15
Subject: Re: Eurodates by default

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