On Thu, 14 Jun 2001, Tom Lane wrote:
> Alex Pilosov <alex@pilosoft.com> writes:
> > Indexpath generated for such an expression is this:
> > (a > network(b)) and (a <= set_masklen(broadcast(b, 32)))
>
> What happens to that set_masklen thing for IPv6?
>
> If the network.c code were exporting a function that made this value,
> I'd not worry; but I don't like wiring an IPv4 assumption into code far
> away in the planner. Can't we do better here? Perhaps move the
> generation of the indexscan bound values into a subroutine in network.c?
Good point. I already rewrote it, but I am going to send it in tomorrow, I
want to resync to HEAD, since some of network.c was taken in and I want to
have a clean patch for you guys :)
Thanks
-alex
