Hi Michael,

Good to know you're keeping an eye on this.

27.03.2026 02:12, Michael Paquier wrote:
Thanks.  That's going to be handy.  One thing I am not sure of is if
Jeff and/or Heikki are planning to come back to this thread by the
feature freeze and do something about it for v19.

I completely understand that committers are very busy and everyone has
their own priorities. I still hope Jeff and/or Heikki will have a chance
to look at this, but given that it’s been over 8 months since the
patches were submitted, I’m trying to be realistic about the v19
feature freeze.

So let's see what happens, but I'll be happy to study this patch
opportunity in v20, be it in a complete form or a partial form (for
the latter we could assume that a portion of what you are suggesting
is committed into the tree in time for v19, leaving some hanging
fruits for v20).

I’m currently studying the Postgres codebase to gain a better
understanding of it and figure out where my experience can be most
useful. However, I’d prefer not to jump from one idea to another and
flood the mailing list with new patches. I’d rather focus on seeing
these current ones through to their logical conclusion before
starting something new.

--
Alexander Borisov



Reply via email to