| From: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>, "Emanuel Calvo" <3manuek(at)esdebian(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Nicolas Barbier" <nicolas(dot)barbier(at)gmail(dot)com>, "Claudio Freire" <klaussfreire(at)gmail(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Andres Freund" <andres(at)2ndquadrant(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BRIN indexes - TRAP: BadArgument |
| Date: | 2014-09-26 16:12:22 |
| Message-ID: | bbef79b1ab78829ec4882f3c0fc92d11.squirrel@webmail.xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, September 23, 2014 21:04, Alvaro Herrera wrote:
> Alvaro Herrera wrote:
>
> [minmax-19.patch]
> [minmax-19a.patch]
Although admittedly it is not directly likely for us to need it, and although I see that there is a BRIN Extensibility
chapter added (good!), I am still a bit surprised by the absence of a built-in BRIN operator class for bigint, as the BRIN
index type is specifically useful for huge tables (where after all huge values are more likely to occur).
Will a brin int8 be added operator class for 9.5? (I know, quite some time left...)
(btw, so far the patch proves quite stable under my abusive testing...)
thanks,
Erik Rijkers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oskari Saarenmaa | 2014-09-26 16:14:03 | Re: Inefficient barriers on solaris with sun cc |
| Previous Message | Stephen Frost | 2014-09-26 15:35:09 | Re: WITH CHECK and Column-Level Privileges |