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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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:43:58
Message-ID: 1239156.1595378638@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> 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?

Didn't really see much point. It's not like anybody's likely to
take out the collation handling now that it's there.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2020-07-22 00:46:59 Re: factorial function/phase out postfix operators?
Previous Message Michael Paquier 2020-07-22 00:36:12 Re: v13 planner ERROR: could not determine which collation to use for string comparison