Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VYNWe-0004Oa-8e for pgsql-students@arkaria.postgresql.org; Mon, 21 Oct 2013 22:00:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VYNWd-0001bo-IS for pgsql-students@arkaria.postgresql.org; Mon, 21 Oct 2013 22:00:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VYNWc-0001bZ-AI; Mon, 21 Oct 2013 22:00:34 +0000 Received: from acidenitrix.villemain.org ([91.121.90.165]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VYNWY-0008N7-92; Mon, 21 Oct 2013 22:00:33 +0000 Received: from [89.157.16.165] (helo=Dimitris-MacBook-Air.local) by acidenitrix.villemain.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1VYNWV-0005rJ-3D; Tue, 22 Oct 2013 00:00:27 +0200 From: Dimitri Fontaine To: Tom Lane Cc: Alexander Korotkov , Heikki Linnakangas , Stas Kelvich , Robert Haas , pgsql-hackers , pgsql-students@postgresql.org Subject: Re: [HACKERS] Cube extension point support // GSoC'13 Organization: 2ndQuadrant References: <23364502-F542-4553-A658-4D3A2B6FCFA9@gmail.com> <5236A9BC.3030000@vmware.com> <5258038C.9070409@vmware.com> <52657B1C.7050906@vmware.com> <3819.1382384476@sss.pgh.pa.us> User-Mail-Address: dimitri@2ndQuadrant.fr Date: Tue, 22 Oct 2013 00:00:24 +0200 In-Reply-To: <3819.1382384476@sss.pgh.pa.us> (Tom Lane's message of "Mon, 21 Oct 2013 15:41:16 -0400") Message-ID: User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (darwin) MIME-Version: 1.0 Content-Type: text/plain 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 Tom Lane writes: > I believe the reason GIST has compress/decompress functions is not for > TOAST (they predate that, if memory serves), but to allow the on-disk > representation of an index entry to be different from the data type's > normal representation in other ways --- think lossy storage in particular. My understanding of the use case for those functions is to do with storing a different data type in the index upper nodes and in the index leafs. It should be possible to do that in a non-lossy way, so that you would implement compress/decompress and not declare the RECHECK bits. Then again I'm talking from 8.3 era memories of when I tried to understand GiST enough to code the prefix extension. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-students mailing list (pgsql-students@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-students