Re: Special-case executor expression steps for common combinations

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>
To: Andreas Karlsson <andreas@proxel.se>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2025-03-09T22:35:40Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add special case fast-paths for strict functions

  2. Replace EEOP_DONE with special steps for return/no return

> On 8 Mar 2025, at 17:15, Andreas Karlsson <andreas@proxel.se> wrote:
> 
> On 2/5/25 11:00 AM, Daniel Gustafsson wrote:
>> This fell off the ever-growing TODO again.  Re-reading it I still think it's a
>> good idea, it applied almost cleanly still and still gives a slight performance
>> improvement along with the more interesting refactoring which will make caching
>> of expressions easier down the line.
>> Attached is a rebased v4, unless there are objections I'll go ahead with this
>> version.
> 
> +1 Still seems like a nice change to me too.

Thanks, I actually had it staged to go in early next week.

--
Daniel Gustafsson