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 CA6283A5F94 for ; Thu, 27 Jan 2005 19:09:50 +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 00100-10 for ; Thu, 27 Jan 2005 19:09:48 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id 8F1523A5FC8 for ; Thu, 27 Jan 2005 19:09:47 +0000 (GMT) Received: (qmail 2750 invoked from network); 27 Jan 2005 20:10:05 +0100 Received: from unknown (HELO musicbox) (boutiquenumerique-lists@192.168.0.2) by boutiquenumerique.com with SMTP; 27 Jan 2005 20:10:05 +0100 To: pgsql-performance@postgresql.org Subject: Re: [SQL] OFFSET impact on Performance??? References: <6EE64EF3AB31D5448D0007DD34EEB3412A75CB@Herge.rcsinc.local> <87brbiah0f.fsf@stark.xeocode.com> <33c6269f0501261035bc87695@mail.gmail.com> <33c6269f05012620427c1ccc40@mail.gmail.com> <87d5vqwwle.fsf@stark.xeocode.com> Message-ID: Date: Thu, 27 Jan 2005 20:11:55 +0100 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 In-Reply-To: <87d5vqwwle.fsf@stark.xeocode.com> 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/553 X-Sequence-Number: 10243 > What you want is called UNNEST. It didn't get done in time for 8.0. But > if > what you have is an array of integers the int_array_enum() function I > quoted > in the other post is basically that. Yes, I used it, thanks. That's what I wanted. The query plans are good. > You don't really need the int_array_aggregate function any more. You can > write > your own aggregate using the new array operators: > Of course it's about 50x slower than the C implementation though: Heh. I'll keep using int_array_aggregate ;) Have a nice day.