Re: Unexpected "cache lookup failed for collation 0" failure

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>, 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-14 04:03:42
Message-ID: 20191114040342.GC1910@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 13, 2019 at 03:56:11PM -0500, Tom Lane wrote:
> 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.

Wouldn't it be better to add a test case for that?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-11-14 04:09:12 Re: Unexpected "cache lookup failed for collation 0" failure
Previous Message PG Bug reporting form 2019-11-14 03:14:00 BUG #16113: pg_dumpall failed on database "中文"