Re: IN, BETWEEN, spec compliance, and odd operator names

From: "Nathan Boley" <npboley(at)gmail(dot)com>
To: "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>
Subject: Re: IN, BETWEEN, spec compliance, and odd operator names
Date: 2008-08-25 19:44:04
Message-ID: 6fa3b6e20808251244v1d22d318gb0a383e7eecc30d2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Yes, but always in relation to operator classes, so from BTrees opclass or
> such, which I refered to as "the context of index searches", as I don't
> really see any theorical need for opclass if it's not for indexing.

IIRC analyze uses the btree op class to build the selectivity histogram.

-Nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2008-08-25 19:54:06 Re: IN, BETWEEN, spec compliance, and odd operator names
Previous Message Tom Lane 2008-08-25 19:43:08 Re: IN, BETWEEN, spec compliance, and odd operator names