Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUzgZ-0005yV-CN for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 20:56:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iUzgX-00061K-P8 for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 20:56:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUzgX-00060I-HA for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 20:56:17 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUzgV-00026m-C9 for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 20:56:17 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xADKuBG9002908; Wed, 13 Nov 2019 15:56:11 -0500 From: Tom Lane To: Manuel Rigger cc: PostgreSQL mailing lists , Peter Eisentraut Subject: Re: Unexpected "cache lookup failed for collation 0" failure In-reply-to: <19497.1573663852@sss.pgh.pa.us> References: <19497.1573663852@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 13 Nov 2019 11:50:52 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2905.1573678571.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Nov 2019 15:56:11 -0500 Message-ID: <2906.1573678571@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > Manuel Rigger writes: >> Is the error "cache lookup failed for collation 0" in this context expe= cted? >> 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