| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | ERROR: could not determine which collation to use for string comparison |
| Date: | 2020-04-14 16:49:11 |
| Message-ID: | VisenaEmail.72.37d08ec2b8cb8fb5.17179940cd3@tc7-visena |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Guys; This errors out with:
ERROR: could not determine which collation to use for string comparison
HINT: Use the COLLATE clause to set the collation explicitly.
The database is init'ed with:
initdb -D $PGDATA -E utf8 --locale=nb_NO.UTF-8
13-dev HEAD as of 8128b0c152a67917535f50738ac26da4f984ddd9
Works fine in <= 12
===========================
create table person( id serial primary key, firstname varchar, lastname varchar
);insert into person(firstname, lastname) values ('Andreas', 'Krogh'); CREATE
OR REPLACE FUNCTIONconcat_lower(varchar, varchar) RETURNS varchar AS $$ SELECT
nullif(lower(coalesce($1, '')) || lower(coalesce($2, '')), '') $$ LANGUAGE SQL
IMMUTABLE; select * from person pers ORDER BY concat_lower(pers.firstname,
pers.lastname)ASC; ===========================
--
Andreas Joseph Krogh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-04-14 16:56:49 | Re: documenting the backup manifest file format |
| Previous Message | Jehan-Guillaume de Rorthais | 2020-04-14 16:09:23 | Re: [BUG] non archived WAL removed during production crash recovery |