| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Subject: | Re: Unexpected "cache lookup failed for collation 0" failure |
| Date: | 2019-11-13 20:56:11 |
| Message-ID: | 2906.1573678571@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> writes:
>> Is the error "cache lookup failed for collation 0" in this context expected?
>> CREATE TABLE t0(c0 CHAR(2) COLLATE "C", c1 CHAR(2) COLLATE "POSIX");
>> INSERT INTO t0 VALUES('', '');
>> SELECT * FROM t0 WHERE t0.c1 NOT IN (t0.c0); -- unexpected: cache
>> lookup failed for collation 0
> I get an assertion failure :-(, although the assertion is just
> complaining about the same thing, ie no-collation-assigned.
> Used to work before v12, too. Looking...
Looks like a simple oversight --- when bpcharne() was made
collation-sensitive, it should have grown a check_collation_set()
call, but somehow that got left out. Fixed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2019-11-13 22:53:28 | Re: BUG #16112: large, unexpected memory consumption |
| Previous Message | Thomas Munro | 2019-11-13 20:20:11 | Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash |