Postgres Pro
Downloads
Home   >   mailing lists

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

From Melanie Plageman
Subject Re: Bug in either collation docs or code
Date
Msg-id CAAKRu_Yqy-_x1joTfd6kB=-uWYHKDcPg=tYPZfadqHTXgF5q1A@mail.gmail.com
Whole thread Raw
In response to Re: Bug in either collation docs or code  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Bug in either collation docs or code
List pgsql-hackers
Tree view


​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.



I tried inserting data and did not get an error:

CREATE TABLE test1 (
    a text COLLATE "de_DE",
    b text COLLATE "es_ES"
);

INSERT INTO test1 VALUES('b','b'), ('c','c'), ('g','g'), ('h','h');
SELECT a < (select 'foo' COLLATE "fr_FR") FROM test1;

--
Melanie Plageman

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Needless additional partition check in INSERT?
Next
From: "David G. Johnston"
Date:
Subject: Re: Bug in either collation docs or code