X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2306A3A5DB5 for ; Thu, 27 Jan 2005 16:42:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 82598-02 for ; Thu, 27 Jan 2005 16:42:09 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id 71F213A57D9 for ; Thu, 27 Jan 2005 16:42:08 +0000 (GMT) Received: (qmail 27907 invoked from network); 27 Jan 2005 17:42:25 +0100 Received: from unknown (HELO musicbox) (boutiquenumerique-lists@192.168.0.2) by boutiquenumerique.com with SMTP; 27 Jan 2005 17:42:25 +0100 Date: Thu, 27 Jan 2005 17:44:15 +0100 To: "Oleg Bartunov" Subject: Re: [SQL] OFFSET impact on Performance??? Cc: alex@neteconomist.com, "Greg Stark" , "Merlin Moncure" , "Andrei Bintintan" , pgsql-performance@postgresql.org References: <6EE64EF3AB31D5448D0007DD34EEB3412A75CB@Herge.rcsinc.local> <87brbiah0f.fsf@stark.xeocode.com> <33c6269f0501261035bc87695@mail.gmail.com> <33c6269f05012620427c1ccc40@mail.gmail.com> From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera M2/7.54 (Linux, build 751) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/542 X-Sequence-Number: 10232 >> However, it seems that integer && integer[] does not exist : > > Try intset(id) && int[]. intset is an undocumented function :) > I'm going to add intset() to README. > >> >>> SELECT * FROM table WHERE id && int[] Mm. intset(x) seems to be like array[x] ? Actually what I want is the opposite. I have a btree index on an integer column ; I wanted to use this index and not create a functional index... which is why I wanted to use =ANY(). If I had a gist index on an integer array column, I would of course use what you suggest, but this is not the case... Anyway I think the SRF function solution works well, I like it. Note that int_agg_final_array() crashes my postgres, see my message in psql/general Regards, Pierre