Re: Convert coalesce to or/and

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Nicolas Adenis-Lamarre <nicolas(dot)adenis(dot)lamarre(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Convert coalesce to or/and
Date: 2026-02-18 11:08:10
Message-ID: 71b6f9b6c00709bc5e815934aa33c94570495034.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2026-02-18 at 10:54 +0100, Nicolas Adenis-Lamarre wrote:
> I didn't get a feedback on this patch.
> I can just remove it if thats not a wanted optimisation for any reason.
> Just to be sure it was not missed or if i should upload it for the
> commit fest or something else.

The approach looks right, but I didn't scrutinize the code.
It is always good to get better estimates!

It's nice if you quote relevant parts of the thread so that people
don't have to search the archives to know what you are talking
about (the subject no longer matches what your patch does).

Yes, you should add it to the commitfest - but you'd have to wait
for the next commitfest to be created. There is an agreement that
you don't add new patches to the final commitfest of a release.

So yours would be considered for v20.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-02-18 11:28:20 Re: [PATCH] Support automatic sequence replication
Previous Message John Naylor 2026-02-18 11:04:09 Re: centralize CPU feature detection