Re: BRIN indexes - TRAP: BadArgument

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: BRIN indexes - TRAP: BadArgument
Дата
Msg-id 545F3149.4050701@vmware.com
обсуждение исходный текст
Ответ на Re: BRIN indexes - TRAP: BadArgument  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: BRIN indexes - TRAP: BadArgument  (Greg Stark <stark@mit.edu>)
Re: BRIN indexes - TRAP: BadArgument  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
On 11/09/2014 08:06 AM, Michael Paquier wrote:
> On Sat, Nov 8, 2014 at 5:40 PM, David Rowley <dgrowleyml@gmail.com> wrote:
>> Please find attached another small fix. This time it's just a small typo in
>> the README, and just some updates to some, now outdated docs.
> Speaking about the feature... The index operators are still named with
> "minmax", wouldn't it be better to switch to "brin"?

All the built-in opclasses still implement the min-max policy - they 
store the min and max values. BRIN supports other kinds of opclasses, 
like storing a containing box for points, but no such opclasses have 
been implemented yet.

Speaking of which, Alvaro, any chance we could get such on opclass still 
included into 9.5? It would be nice to have one, just to be sure that 
nothing minmax-specific has crept into the BRIN code.

- Heikki



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: BRIN indexes - TRAP: BadArgument
Следующее
От: Andreas Joseph Krogh
Дата:
Сообщение: Re: Support for detailed description of errors cased by trigger-violations