| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: comparison operators |
| Date: | 2014-06-18 13:24:38 |
| Message-ID: | 10933.1403097878@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
>> I think I'd rather just say "for many data types" or something along
>> those lines, rather than imply that there is some obvious rule that
>> users should be able to intuit.
> Perhaps with a link to where the informaiton about which exist is
> available..? Or a query to get the list?
Queries for this sort of thing are covered in the chapter about index
opclasses. The basic query would be like
select opcintype::regtype from pg_opclass where opcmethod = 403 and opcdefault;
but I'm not sure if this is completely useful; it's not obvious for
example that the "text" opclass is also used for varchar. Another
point is that some of the operators aren't named in the conventional
way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-06-18 13:25:37 | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |
| Previous Message | Robert Haas | 2014-06-18 13:13:51 | Re: WAL replay bugs |