From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Is there bigintarray? |
Date: | 2015-11-02 22:28:25 |
Message-ID: | CAMkU=1zmxAQLPe9HHuCgddNyxGhBa_Gouny4anqmoaZ0npaKSg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Nov 2, 2015 at 1:41 PM, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> Igor Bossenko schrieb am 02.11.2015 um 14:20:
>>
>> What is the current plans for bigintarray?
>>
>> Igor
>>
>>
>
> The following works for me:
>
> create table foo
> (
> bia bigint[]
> );
But you can't build indexes on them using the intarray extension
opclasses, which I think is what he wants to know about. There is
gist__intbig_ops, but that is for big arrays of ints, not for arrays
of bigints.
As far as I know there are no plans on this front.
If Igor only needs &&, @> and <@ then he can just use the builtin gin
opclass for those. But he can't get @@ and ~~ from the built-ins.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Jason O'Donnell | 2015-11-02 22:56:12 | Re: How to search a string inside a json structure |
Previous Message | David G. Johnston | 2015-11-02 22:22:31 | Re: Approach to extract top records from table based upon aggregate |