pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ERROR:  could not determine which collation to use for string comparison
4+ messages / 4 participants
[nested] [flat]

Commits from this thread:
  2020-04-14 2d59643dbc  Account for collation when coercing the output of a SQL function.
* ERROR:  could not determine which collation to use for string comparison
@ 2020-04-14 16:49 Andreas Joseph Krogh <andreas@visena.com>
  2020-04-14 21:31 ` Re: ERROR: could not determine which collation to use for string comparison Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Andreas Joseph Krogh @ 2020-04-14 16:49 UTC (permalink / raw)
  To: pgsql-hackers@lists.postgresql.org


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 

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: ERROR: could not determine which collation to use for string comparison
  2020-04-14 16:49 ERROR:  could not determine which collation to use for string comparison Andreas Joseph Krogh <andreas@visena.com>
@ 2020-04-14 21:31 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Tom Lane @ 2020-04-14 21:31 UTC (permalink / raw)
  To: Andreas Joseph Krogh <andreas@visena.com>; +Cc: pgsql-hackers@lists.postgresql.org

Andreas Joseph Krogh <andreas@visena.com> writes:
> 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.

Fixed, thanks for the report.

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* ERROR: could not determine which collation to use for string comparison
@ 2023-06-06 14:42 Rômulo Coutinho <romulo@supersim.com.br>
  2023-06-06 16:57 ` Re: ERROR: could not determine which collation to use for string comparison Laurenz Albe <laurenz.albe@cybertec.at>
  0 siblings, 1 reply; 4+ messages in thread

From: Rômulo Coutinho @ 2023-06-06 14:42 UTC (permalink / raw)
  To: pgsql-hackers@lists.postgresql.org

Hi,

We recently upgraded to Postgres 15.3. When running ANALYZE, we get the
following message:
ERROR:  could not determine which collation to use for string comparison
HINT:  Use the COLLATE clause to set the collation explicitly.

We have never seen this before. Could this be a bug?

Regards,

Rômulo Coutinho.

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: ERROR: could not determine which collation to use for string comparison
  2023-06-06 14:42 ERROR: could not determine which collation to use for string comparison Rômulo Coutinho <romulo@supersim.com.br>
@ 2023-06-06 16:57 ` Laurenz Albe <laurenz.albe@cybertec.at>
  0 siblings, 0 replies; 4+ messages in thread

From: Laurenz Albe @ 2023-06-06 16:57 UTC (permalink / raw)
  To: Rômulo Coutinho <romulo@supersim.com.br>; pgsql-hackers@lists.postgresql.org

On Tue, 2023-06-06 at 11:42 -0300, Rômulo Coutinho wrote:
> We recently upgraded to Postgres 15.3. When running ANALYZE, we get the following message:
> ERROR:  could not determine which collation to use for string comparison
> HINT:  Use the COLLATE clause to set the collation explicitly.
> 
> We have never seen this before. Could this be a bug?

Impossible to say without a way to reproduce.

Yours,
Laurenz Albe





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2023-06-06 16:57 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-04-14 16:49 ERROR:  could not determine which collation to use for string comparison Andreas Joseph Krogh <andreas@visena.com>
2020-04-14 21:31 ` Re: ERROR: could not determine which collation to use for string comparison Tom Lane <tgl@sss.pgh.pa.us>
2023-06-06 14:42 ERROR: could not determine which collation to use for string comparison Rômulo Coutinho <romulo@supersim.com.br>
2023-06-06 16:57 ` Re: ERROR: could not determine which collation to use for string comparison Laurenz Albe <laurenz.albe@cybertec.at>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox