Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate
Date: 2025-04-07 13:50:42
Message-ID: CAAKRu_bkxv3cXhnhDpNbKVVKrR70Nh-oJxJdeiW3_O2kS0pbBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Mon, Apr 7, 2025 at 5:15 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

> Are these failures from patches applied to master prior to 3ba2cdaa?

Yea, my email was held in moderation for days. I guess cross-posting is
flagged. I thought I saw people regularly cc pgsql-hackers when replying to
pgsql-committers, but I guess not.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2025-04-07 15:03:10 pgsql: Revert "Use workaround of __builtin_setjmp only on MINGW on MSVC
Previous Message Andres Freund 2025-04-07 13:45:25 pgsql: read_stream: Fix overflow hazard with large shared buffers

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-04-07 13:59:19 Re: [PoC] Federated Authn/z with OAUTHBEARER
Previous Message Andres Freund 2025-04-07 13:43:01 Re: ci: Allow running mingw tests by default via environment variable