I don't understand why you object the idea giving PostgreSQL the
ability to turn off the locale support in configuration/compile
time. In that way, there's no inconveniences for many users.
I don't mind at all the ability to turn it off. My point is that the
compile time is the wrong
DBMS should be independent from the OS settings as far as
possible especially in the handling of data. Currently we
could hardly judge if we are running on a locale or not from
the dbms POV and it doesn't seem a dbms kind of thing in the
first place. I'm a dbms guy not an OS guy and really
Tatsuo Ishii writes:
I don't understand why you object the idea giving PostgreSQL the
ability to turn off the locale support in configuration/compile
time. In that way, there's no inconveniences for many users.
I don't mind at all the ability to turn it off. My point is that the
compile
Hiroshi Inoue writes:
I would object even if there's such a way.
People in Japan have hardly noticed that the strange
behabior is due to the strange locale(LC_COLLATE).
I don't think we should design our systems in a way that inconveniences
many users because some users are using broken
I would object even if there's such a way.
People in Japan have hardly noticed that the strange
behabior is due to the strange locale(LC_COLLATE).
I don't think we should design our systems in a way that
inconveniences
many users because some users are using broken operating systems.
Face it, everything has locale support these day. PostgreSQL is one
of
the few packages that even has it as an option to turn it off. Users
of
binary packages of PostgreSQL are all invariably faced with locale
features. So it's not like sudden unasked-for locale support is going
to
be a
Tatsuo Ishii writes:
Tatsuo Ishii writes:
I wouldn't object it if there is a way to disable locale support.
export LC_ALL=C
It's not a solution. My point is people should not be troubled by the
useless feature (at least for Japanese) even if they set their locale
other than C.
If
Zeugswetter Andreas SB SD writes:
What makes you so opposed to a GUC for disabling locale support ?
Nothing. It may in fact be the best solution.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of
If people set their locale to something other than C they have evidently
judged that locale is not useless. Why would they set it otherwise?
As Hiroshi pointed out, the broken thing is the LC_COLLATE, other
things in the local are working.
I
don't think hiding away a feature because you
Hiroshi Inoue writes:
I would object even if there's such a way.
People in Japan have hardly noticed that the strange
behabior is due to the strange locale(LC_COLLATE).
I don't think we should design our systems in a way that inconveniences
many users because some users are using
Peter Eisentraut [EMAIL PROTECTED] writes:
Zeugswetter Andreas SB SD writes:
What makes you so opposed to a GUC for disabling locale support ?
Nothing. It may in fact be the best solution.
As long as locale has to be an initdb-time setting, a GUC var won't
help much.
Peter Eisentraut wrote:
Hiroshi Inoue writes:
I would object even if there's such a way.
People in Japan have hardly noticed that the strange
behabior is due to the strange locale(LC_COLLATE).
I don't think we should design our systems in a way that inconveniences
many users because
Tatsuo Ishii writes:
I wouldn't object it if there is a way to disable locale support.
export LC_ALL=C
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 5: Have you checked our extensive
Peter Eisentraut wrote:
Tatsuo Ishii writes:
I wouldn't object it if there is a way to disable locale support.
export LC_ALL=C
I would object even if there's such a way.
People in Japan have hardly noticed that the strange
behabior is due to the strange locale(LC_COLLATE).
regards,
Tatsuo Ishii writes:
I wouldn't object it if there is a way to disable locale support.
export LC_ALL=C
It's not a solution. My point is people should not be troubled by the
useless feature (at least for Japanese) even if they set their locale
other than C.
--
Tatsuo Ishii
Hi Peter,
Any idea of how many extra memory moving operations that would be?
:-)
Regards and best wishes,
Justin Clift
Peter Eisentraut wrote:
It occurred to me that a server with locale features that is started in
the C locale is going to behave the same as a server without locale
Peter Eisentraut [EMAIL PROTECTED] writes:
(I sincerely hope that all systems' libcs have optimized paths for the C
locale.) So we could get rid of this --enable-locale switch
altogether.
Some experimental evidence to support the claim that --enable-locale has
zero cost would be good before
If it's of any assistance, I'm working with the Open Source Database
Benchmark guys (osdb.sourceforge.net) to get an AS3AP-based benchmark
for PostgreSQL 7.1.x+ up-and-running reliably.
It's working on my Mandrake Linux 8.0 system here, but I need the main
OSDB guy to get back from holidays to
It occurred to me that a server with locale features that is started in
the C locale is going to behave the same as a server without locale
features. The exception are a few extra memory moving operations. (I
sincerely hope that all systems' libcs have optimized paths for the C
locale.)
19 matches
Mail list logo
