| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Alexander Nestorov <alexandernst(at)gmail(dot)com> |
| Cc: | Maxime Schoemans <maxime(dot)schoemans(at)enterprisedb(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] btree_gist: add cross-type integer operator support for GiST |
| Date: | 2026-06-26 11:13:52 |
| Message-ID: | 9CD290B1-C382-46CB-9ADE-CE6B039EBB25@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 26 Jun 2026, at 01:07, Alexander Nestorov <alexandernst(at)gmail(dot)com> wrote:
>
> Fantastic!! From what I understood, this will land in PG20. Is there any date limit (merge window)
> for that? If "no", let's give Andrey a chance to have another look at the patchset (he told me
> he is currently overloaded). If "yes" (and we're close to the end of it), let's set it to "Ready" in
> order to avoid slipping outside of the merge window.
> By the way, should I set the status?
The decision to commit something is up to the committers. They normally look
for useful new patches in the Commitfest, our app for tracking proposed contributions.
Any community reviewer - like Maxime or me - can move an entry to "Ready for Committer";
sometimes that attracts a committer's attention, sometimes it doesn't. You can change
the status yourself, but "Ready for Committer" is best set by a reviewer once they're
happy with the patch. Personally, I consider setting "RfC" on my side as a contract
for "I'll show up to fix stuff if we break something by committing this". But there are
no written rules AFAIK.
I'm a bit overloaded to do another review round right this moment (but I still skim
pgsql-hackers - that's my way of filling the gaps between managerial meetings). I plan
to get to this patchset soon, as soon as I'm back to regular hacking; I have two more
prioritized hacking tasks ahead of it, though.
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shlok Kyal | 2026-06-26 12:38:27 | Re: Support EXCEPT for ALL SEQUENCES publications |
| Previous Message | Henson Choi | 2026-06-26 11:12:15 | Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks |