Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cZ3Gt-0004lb-3i for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Feb 2017 22:20:59 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cZ3Gs-00043X-Mi for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Feb 2017 22:20:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cZ3FT-0002Pp-2p for pgsql-hackers@postgresql.org; Wed, 01 Feb 2017 22:19:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cZ3FP-00053O-Ro for pgsql-hackers@postgresql.org; Wed, 01 Feb 2017 22:19:30 +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 v11MJOwJ019519; Wed, 1 Feb 2017 17:19:24 -0500 From: Tom Lane To: Alvaro Herrera cc: Pavan Deolasee , pgsql-hackers Subject: Re: Patch: Write Amplification Reduction Method (WARM) In-reply-to: <20170201213144.xb64zuem6azqntrs@alvherre.pgsql> References: <20170201213144.xb64zuem6azqntrs@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 01 Feb 2017 18:31:44 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19517.1485987564.1@sss.pgh.pa.us> Date: Wed, 01 Feb 2017 17:19:24 -0500 Message-ID: <19518.1485987564@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Alvaro Herrera writes: > Tom Lane wrote: >> I think what we ought to do about this is invent additional API >> functions, say >> >> Oid CatalogTupleInsertWithInfo(Relation heapRel, HeapTuple tup, >> CatalogIndexState indstate); >> void CatalogTupleUpdateWithInfo(Relation heapRel, ItemPointer otid, >> HeapTuple tup, CatalogIndexState indstate); >> >> and use these in place of simple_heap_foo plus CatalogIndexInsert >> in the places where this optimization had been applied. > This looks reasonable enough to me. Done. 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