Re: [PG19] Wrong results from Memoize with a nondeterministic collation

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Guofenglinux <guofenglinux(at)gmail(dot)com>
Subject: Re: [PG19] Wrong results from Memoize with a nondeterministic collation
Date: 2026-11-04 00:46:46
Message-ID: CAApHDvrF=+rJ2Q_eOiQqgbrOHwruKRfPjZ3OLsDvi3i+AQPApg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 8 Oct 2026 at 16:33, shihao zhong <zhong950419(at)gmail(dot)com> wrote:
> Since 0da29e4cb16 an anti join can use Memoize. Memoize compares its
> cache key with the collation of o.code, so 'P1' hits the cache entry
> of 'p1'. The clause compares under "C", where they differ.

I made a few minor adjustments and pushed this. Thanks.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-11-04 00:52:32 Re: [PATCH v1] Fix initial sync of zero-column published tables
Previous Message surya poondla 2026-11-04 00:40:47 Re: Reject unsupported COPY FROM targets before analyzing WHERE clause