Re: Bug in either collation docs or code - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Bug in either collation docs or code
Date
Msg-id CAKFQuwYVLdBX5NE0L5rER=rFXNy1rO-_1oBeYPcj84ujCxSiWQ@mail.gmail.com
Whole thread Raw
In response to Re: Bug in either collation docs or code  (Melanie Plageman <melanieplageman@gmail.com>)
Responses Re: Bug in either collation docs or code
Re: Bug in either collation docs or code
List pgsql-hackers
On Thu, Jun 7, 2018 at 4:37 PM, Melanie Plageman <melanieplageman@gmail.com> wrote:
CREATE TABLE test1 (   a text COLLATE "de_DE",   b text COLLATE "es_ES",   ...
);

My thought was to add the following example:

SELECT a < (select 'foo' COLLATE "fr_FR") FROM test1;

I thought this would error out because the subquery's result is considered implicit and, in this case, it seems you now have conflicting implicit collations. However, this does not produce an error. What am I missing?


​Data, apparently...I got the same non-error result before inserting a record into test1 then I got the expected error.

Its the function/operator the fails when faced with invalid input, not the planner, so the error requires data to provoke.

David J.


pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Bug in either collation docs or code
Next
From: David Rowley
Date:
Subject: Re: Performance regression with PostgreSQL 11 and partitioning