| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types - cache lookup failed for function |
| Date: | 2011-02-07 16:52:51 |
| Message-ID: | 1297097571.27157.163.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2011-02-06 at 20:10 +0100, Erik Rijkers wrote:
> I was trying
> where intrange @> integer
>
> which admittedly is not in the documentation,
> but does already half work, and would be really
> convenient to have. As it stands the construct
> seems to fail after ANALYZE, when there is more
> than 1 row:
Thank you for the report! I actually did make some mention of that in
the documentation, albeit brief (in the operators table, using timestamp
as an example).
I have a fix for it. There may still be an issue with the constructors
like range(1,2), so I'll look into it a little more, but an updated
patch should come soon.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-07 16:53:42 | Re: More extension issues: ownership and search_path |
| Previous Message | Florian Pflug | 2011-02-07 16:51:03 | Re: A different approach to extension NO USER DATA feature |