Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UXfSp-00053q-IT for pgsql-students@arkaria.postgresql.org; Wed, 01 May 2013 22:25:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UXfSp-00021m-2b for pgsql-students@arkaria.postgresql.org; Wed, 01 May 2013 22:25:27 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UXfSo-00021h-JH for pgsql-students@postgresql.org; Wed, 01 May 2013 22:25:26 +0000 Received: from mail.gransy.com ([2001:1528:137::f1]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UXfSm-0007Fp-0W for pgsql-students@postgresql.org; Wed, 01 May 2013 22:25:25 +0000 Received: from antispam.gransy.com (antispam.gransy.com [77.78.104.124]) by mail.gransy.com (Postfix) with ESMTP id 73891508B78 for ; Thu, 2 May 2013 00:25:23 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at antispam.gransy.com Received: from mail.gransy.com ([82.208.44.189]) by antispam.gransy.com (antispam.gransy.com [77.78.104.124]) (amavisd-new, port 10024) with ESMTP id rtBSk99OInNE for ; Thu, 2 May 2013 00:25:22 +0200 (CEST) Received: by mail.gransy.com (Postfix, from userid 5000) id 0124D508B7F; Thu, 2 May 2013 00:25:22 +0200 (CEST) Received: from [192.168.1.237] (ip-78-45-133-255.net.upcbroadband.cz [78.45.133.255]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.gransy.com (Postfix) with ESMTPSA id C9AFB508B78 for ; Thu, 2 May 2013 00:25:22 +0200 (CEST) Message-ID: <51819653.2010400@fuzzy.cz> Date: Thu, 02 May 2013 00:25:23 +0200 From: Tomas Vondra User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: pgsql-students@postgresql.org Subject: Re: Another idea for GSoC indexing project References: <43840.1366814309.14128536529105977344@ffe16.ukr.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-students Precedence: bulk Sender: pgsql-students-owner@postgresql.org On 24.4.2013 17:05, Alexander Korotkov wrote: >=20 > On Wed, Apr 24, 2013 at 6:38 PM, =D0=91=D0=BE=D1=87=D0=B5=D1=87=D0=BA=D0= =BE =D0=90=D1=80=D1=81=D0=B5=D0=BD=D0=B8=D0=B9 > wrote: >=20 > Sounds interesting, but this will also require a wrapper for this > composite types? >=20 > For SQL and PL/pgSQL it's not. I'm not sure about rest of procedural > languages. Should be checked. This seems like a really neat project idea, however as I have never used GIN/GiST APIs, I can't really judge the benefits. Could someone prepare a simple example of a simple composite type and implementation of GIN/GiST index with the current and new APIs? Not a complete implementation, just a simple example of how the new API would make it more simple. BTW I think the project should include a simple benchmark, comparing the old C APIs and the new PL APIs. kind regards Tomas --=20 Sent via pgsql-students mailing list (pgsql-students@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-students