Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bUGyG-0000oi-9G for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Aug 2016 17:25:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bUGyF-0003g1-FV for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Aug 2016 17:25:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bUGws-00020Z-Qd for pgsql-hackers@postgresql.org; Mon, 01 Aug 2016 17:24:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bUGwq-0003zR-Cr for pgsql-hackers@postgresql.org; Mon, 01 Aug 2016 17:24:17 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u71HOAPt013192; Mon, 1 Aug 2016 13:24:10 -0400 From: Tom Lane To: Tomas Vondra cc: Aleksander Alekseev , Pavel Stehule , PostgreSQL Hackers , David Steele Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) In-reply-to: <26c3bc60-6613-e7ab-517a-53136f01fb6c@2ndquadrant.com> References: <20160729141552.4062e19b@fujitsu> <39b0f423-a4df-3564-3b4a-b1de6f9eea80@2ndquadrant.com> <1184.1469890030@sss.pgh.pa.us> <5cdc3fde-d6a5-f0d2-b930-485bdcaecde5@2ndquadrant.com> <20160801124531.66cde374@fujitsu> <26c3bc60-6613-e7ab-517a-53136f01fb6c@2ndquadrant.com> Comments: In-reply-to Tomas Vondra message dated "Mon, 01 Aug 2016 15:09:01 +0200" Date: Mon, 01 Aug 2016 13:24:10 -0400 Message-ID: <13191.1470072250@sss.pgh.pa.us> X-Pg-Spam-Score: -3.1 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Tomas Vondra writes: > What is needed is an overview of the approach, so that the reviewers can > read that first, instead of assembling the knowledge from pieces > scattered over comments in many pieces. But I see the fasttab.c contains > this: > /* TODO TODO comment the general idea - in-memory tuples and indexes, > hooks principle, FasttabSnapshots, etc */ A fairly common answer when some feature needs an implementation overview is to create a README file for it, or add a new section in an existing README file. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers