Re: inet/cidr type comparisons

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alex Pilosov <alex(at)pilosoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: inet/cidr type comparisons
Date: 2001-06-11 18:13:45
Message-ID: 5651.992283225@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alex Pilosov <alex(at)pilosoft(dot)com> writes:
> On Mon, 11 Jun 2001, Tom Lane wrote:
>> While there may not be a user-visible function for next-network-part,
>> that hardly matters since the special-indexqual stuff isn't user-visible
>> either.

> Well, since I'm making an indexqual clause, I do need a valid pg_proc id
> there.

No, you need a constant there.

> It can't be resolved during the planning (directfunctioncall) because I do
> want queries of a << b (b isn't a constant) to be also using the same
> mechanism. (so far it looks like special_index_* can cope with that OK)

You're mistaken ... that's not supported currently.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren Johnson 2001-06-11 18:18:15 PostgreSQL Replication
Previous Message mlw 2001-06-11 18:11:06 Re: OID Wrap