scott.marlowe wrote:
On Fri, 6 Jun 2003, Bruce Momjian wrote:
scott.marlowe wrote:
On Fri, 6 Jun 2003, Peter Eisentraut wrote:
scott.marlowe writes:
If indexes on text worked right in other locales it would be no big deal.
They will in version 7.4, so all these
On Fri, 6 Jun 2003, Bruce Momjian wrote:
scott.marlowe wrote:
On Fri, 6 Jun 2003, Peter Eisentraut wrote:
scott.marlowe writes:
If indexes on text worked right in other locales it would be no big deal.
They will in version 7.4, so all these concerns about trading off
On Thu, Jun 05, 2003 at 09:44:21AM -0600, scott.marlowe wrote:
On Thu, 5 Jun 2003, Nigel J. Andrews wrote:
Everything Nigel just wrote plus one thing.
If it comes down to it, we could always require a --locale setting and
refuse to initdb without it. That way, whether it's in an RPM or
On Thu, 5 Jun 2003, Peter Eisentraut wrote:
scott.marlowe writes:
If it comes down to it, we could always require a --locale setting and
refuse to initdb without it. That way, whether it's in an RPM or from
source, somebody somewhere along the line has to choose something.
By
scott.marlowe writes:
If it comes down to it, we could always require a --locale setting and
refuse to initdb without it. That way, whether it's in an RPM or from
source, somebody somewhere along the line has to choose something.
By default, you choose when you install or configure your
scott.marlowe writes:
If indexes on text worked right in other locales it would be no big deal.
They will in version 7.4, so all these concerns about trading off locale
use vs. performance will become obsolete.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of
On Thu, 5 Jun 2003, Alvaro Herrera Munoz wrote:
On Thu, Jun 05, 2003 at 09:44:21AM -0600, scott.marlowe wrote:
On Thu, 5 Jun 2003, Nigel J. Andrews wrote:
Everything Nigel just wrote plus one thing.
If it comes down to it, we could always require a --locale setting and
refuse to
On Thu, 5 Jun 2003, Nigel J. Andrews wrote:
On Wed, 4 Jun 2003, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
That is one thing I liked about the initdb mention --- it clearly told
them to watch out for something they might not have been looking for.
Only if they read
On Fri, 6 Jun 2003, Peter Eisentraut wrote:
scott.marlowe writes:
If indexes on text worked right in other locales it would be no big deal.
They will in version 7.4, so all these concerns about trading off locale
use vs. performance will become obsolete.
Oh! I thought there were still
scott.marlowe wrote:
On Fri, 6 Jun 2003, Peter Eisentraut wrote:
scott.marlowe writes:
If indexes on text worked right in other locales it would be no big deal.
They will in version 7.4, so all these concerns about trading off locale
use vs. performance will become obsolete.
On Wed, 4 Jun 2003, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
That is one thing I liked about the initdb mention --- it clearly told
them to watch out for something they might not have been looking for.
Only if they read the message, though. People who are running RPM
On Wed, Jun 04, 2003 at 11:05:03PM -0400, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
That is one thing I liked about the initdb mention --- it clearly told
them to watch out for something they might not have been looking for.
Only if they read the message, though. People who
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
That is one thing I liked about the initdb mention --- it clearly told
them to watch out for something they might not have been looking for.
Only if they read the message, though. People who are running RPM
installations probably
Peter Eisentraut wrote:
Bruce Momjian writes:
How are people going to know to use these special LIKE indexes?
The same way they presumably find out about anything else: RTFM. A couple
of more cross-references and index entries need to be added, though.
Well, this isn't one of those, How
Bruce Momjian [EMAIL PROTECTED] writes:
That is one thing I liked about the initdb mention --- it clearly told
them to watch out for something they might not have been looking for.
Only if they read the message, though. People who are running RPM
installations probably never get to see what
Tom Lane writes:
I think that a more general solution would be the ability to select a
locale (and hence a sort order) per-column, as the SQL spec envisions.
It is a general solution, but not for this problem. The problem was to
make all locales equally suitable for certain optimizations, not
Bruce Momjian writes:
Our default indexes will be able to do =, , , ORDER BY, and the
special index will be able to do LIKE, ORDER BY, and maybe equals. Do I
have that correct?
The default operator class supports comparisons (=, , , etc.) and ORDER
BY based on those operators. The other
Tom Lane writes:
Are there any locales that claim that not-physically-identical strings
are equal?
In Unicode there are plenty such combinations.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our
Peter Eisentraut wrote:
Bruce Momjian writes:
Our default indexes will be able to do =, , , ORDER BY, and the
special index will be able to do LIKE, ORDER BY, and maybe equals. Do I
have that correct?
The default operator class supports comparisons (=, , , etc.) and ORDER
BY based on
Peter Eisentraut [EMAIL PROTECTED] writes:
I don't understand why you call this a hack. Pattern matching and string
comparison simply work differently, so the proper solution is to use
different operator classes. After all, that's what operator classes exist
for. What is left to be desired?
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Has the single-byte LIKE penalty been eliminated, so we don't need to
consider using C as the default locale for initdb, right?
I'm still of the opinion that we should make C the default locale.
But I'm not sure where the consensus
Bruce Momjian [EMAIL PROTECTED] writes:
So, my understanding is that you would create something such as:
CREATE INDEX iix ON tab (LIKE col)
and that does LIKE lookups and knows how to do col LIKE 'abc%', but it
can't be used for = or ORDER BY, but it can be used for equality tests?
Hm.
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
So, my understanding is that you would create something such as:
CREATE INDEX iix ON tab (LIKE col)
and that does LIKE lookups and knows how to do col LIKE 'abc%', but it
can't be used for = or ORDER BY, but it can be used for
Has the single-byte LIKE penalty been eliminated, so we don't need to
consider using C as the default locale for initdb, right?
If fixed, how was it done?
---
Peter Eisentraut wrote:
Tom Lane writes:
I recall someone
Bruce Momjian [EMAIL PROTECTED] writes:
Has the single-byte LIKE penalty been eliminated, so we don't need to
consider using C as the default locale for initdb, right?
I'm still of the opinion that we should make C the default locale.
But I'm not sure where the consensus is, so I've not made
Tom Lane writes:
Peter has provided a hack whereby one can create a LIKE-supporting index
in a non-C locale. But a *default* index in a non-C locale is still not
going to support LIKE ... and the hacked index will not support ordinary
comparison or ordering operators. So I think there's
26 matches
Mail list logo
