Re: v13 planner ERROR: could not determine which collation to use for string comparison

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: v13 planner ERROR: could not determine which collation to use for string comparison
Date: 2020-07-22 00:36:12
Message-ID: 20200722003612.GC9642@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 21, 2020 at 06:25:00PM -0400, Tom Lane wrote:
> Ugh. It's clear from your stack trace that neqjoinsel() has forgotten to
> pass through collation to eqjoinsel(). Will fix.

Why didn't you include a regression test in bd0d893?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-22 00:43:58 Re: v13 planner ERROR: could not determine which collation to use for string comparison
Previous Message Michael Paquier 2020-07-22 00:31:12 Re: Which SET TYPE don't actually require a rewrite