On 6/13/21 7:43 AM, Alexander Korotkov wrote: > On Sun, Jun 13, 2021 at 2:58 AM Alexander Korotkov <aekorot...@gmail.com> > wrote: >> On Sun, Jun 13, 2021 at 1:16 AM Jonathan S. Katz <jk...@postgresql.org> >> wrote:
>>> Again, I'll defer to others on the code, but this seems to solve the use >>> case I presented. Thanks for the quick turnaround! >> >> Thank you for the feedback! > > I've added the commit message to the patch. I'm going to push it if > no objections. I went ahead and tried testing a few more cases with the patch, and everything seems to work as expected. I did skim through the code -- I'm much less familiar with this part of the system -- and I did not see anything that I would consider "obvious to correct" from my perspective. So I will continue to go with what I said above: no objections on the use case perspective, but I defer to others on the code. One question: if I were to make a custom multirange type (e.g. let's say I use "inet" to make "inetrange" and then a "inetmultirange") will this method still work? It seems so, but I wanted clarify. Thanks, Jonathan
OpenPGP_signature
Description: OpenPGP digital signature
