Re: [HACKERS] clang and LLVM
Firebird http://mapopa.blogspot.com/2010/10/clang-compiling-successful-experiments.html Regards Alexandre Riveira Tom Lane escreveu: Gevik Babakhani pg...@xs4all.nl writes: I was wondering if there has been anyone experimenting to compile PG using LLVM/clang compiler tools. There is (or was, not sure if it's up right now) a buildfarm machine using LLVM. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Per-column collation
Please It would be very important to us that the Brazilian LIKE collate worked with, and possible case-insensitive and accent-insensitive Tank's Alexandre Riveira Brazil Peter Eisentraut escreveu: On mån, 2010-12-06 at 10:01 -0800, David E. Wheeler wrote: I've been wondering if this patch will support case-insensitve collations. If so, then citext should probably be revised to use one. This has been touch upon several times during the discussions on past patches. Essentially, the current patch only arranges that you can specify a sort order for data. The system always breaks ties using a binary comparison. This could conceivably be changed, but it's a separate problem. Some of the necessary investigation work has presumably already been done in the context of citext. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] create custom collation from case insensitive portuguese
Thank you all for your help !
When mentioned in Portuguese case-insensitive in fact we are also
talking about accent-insensitive
A common example is that the name Jose and José also can be written,
citext or ilike only not solve the problem
My progress is ...
Edit file /usr/share/i18n/locales/i18n e alter section tolower /, an
example:
(U00C9,U00E9) e alter for (U00C9,U0065)
LOWER reproduce: LOWER(ITAPAGÉ) = itapage,
Example success:
SELECT * FROM endereco WHERE LOWER(logradouro) LIKE LOWER('itapage%')
this behavior is reproduced in citext (logradouro is column citext)
SELECT * FROM endereco WHERE logradouro = 'itapage'
or
SELECT * FROM endereco WHERE logradouro LIKE 'itapage%'
All examples return the desired value ITAPAGÉ
Issue:
SELECT * FROM endereco WHERE logradouro LIKE 'itapage%' NOT USE INDEX
I tried
CREATE INDEX cep_ik_logradouro ON cep USING btree (logradouro);
CREATE INDEX like_index ON cep(logradouro varchar_pattern_ops);
CREATE INDEX cep_ci_index ON cep(lower(logradouro) varchar_pattern_ops);
I've had success with using index
SELECT * FROM endereco WHERE LOWER(logradouro) LIKE LOWER('itapage%')
and CREATE INDEX cep_ci_index ON cep(lower(logradouro) varchar_pattern_ops)
But I want to solve using only citext
Tank's
Alexandre Riveira
Brazil
Robert Haas escreveu:
On Tue, Nov 2, 2010 at 8:40 AM, Euler Taveira de Oliveira
eu...@timbira.com wrote:
Alexandre Riveira escreveu:
I've achieved some success in changing collate operating system (linux)
to generate sort of way of Brazil Portuguese hopes by adding the
following code in LC_COLLATE
This was already discussed; search the archives [1] [2].
So far, I understood the mechanism of change collate and reproduce in
postgresql, and I could not generate a case-insensitive search, I
believe that would change within the LC_COLLATE variable, but could not
go any further than that.
PostgreSQL doesn't support case-insensitive searches specifying the collate
per column yet. Look at [3]. But you could use ILIKE or regular expression to
achieve that.
Is citext also useful for this?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] create custom collation from case insensitive portuguese
Thanks to all the work they have done with this incredible database, postgresql. I've achieved some success in changing collate operating system (linux) to generate sort of way of Brazil Portuguese hopes by adding the following code in LC_COLLATE LC_COLLATE copy iso14651_t1_ci reorder-after U00A0 U0020 CAP; CAP; CAP; U0020 reorder-end And in my tests I could change the behavior of the postgresql UPPER changing the file i18n ... etc. toupper / (U0061, U0041); So far, I understood the mechanism of change collate and reproduce in postgresql, and I could not generate a case-insensitive search, I believe that would change within the LC_COLLATE variable, but could not go any further than that. Could someone guide me please. Thanks, Alexandre Riveira Brazil -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] create custom collation from case insensitive portuguese
Thanks to all the work they have done with this incredible database, postgresql. I've achieved some success in changing collate operating system (linux) to generate sort of way of Brazil Portuguese hopes by adding the following code in LC_COLLATE LC_COLLATE copy iso14651_t1_ci reorder-after U00A0 U0020 CAP; CAP; CAP; U0020 reorder-end And in my tests I could change the behavior of the postgresql UPPER changing the file i18n ... etc. toupper / (U0061, U0041); So far, I understood the mechanism of change collate and reproduce in postgresql, and I could not generate a case-insensitive search, I believe that would change within the LC_COLLATE variable, but could not go any further than that. Could someone guide me please. Thanks, Alexandre Riveira Brazil -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
