Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cYbwa-0001PL-0h for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Jan 2017 17:10:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cYbwY-0005dy-IE for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Jan 2017 17:10:10 +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 1cYbwW-0005bm-BS for pgsql-hackers@postgresql.org; Tue, 31 Jan 2017 17:10:08 +0000 Received: from mail-qt0-x22f.google.com ([2607:f8b0:400d:c0d::22f]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cYbwT-0005x6-2U for pgsql-hackers@postgresql.org; Tue, 31 Jan 2017 17:10:06 +0000 Received: by mail-qt0-x22f.google.com with SMTP id x49so238606649qtc.2 for ; Tue, 31 Jan 2017 09:10:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=Z6wMa8Qnzo3eXBmC/3WSOjxL8GTI/OCh7ZtmfhJjomM=; b=zb9jj5FsGc8o3HMjK0R+OmiJ8ugi5y6btm7/EVIdcLK8kGznvkCM1fJHhB+/cBxZSn 3viT8bGgCxPf3P7VnZNI4vxvw3PJXaJcdgPt3zupMb+O0CZOTgp50I7rLcCPwQM0Li1t KaK1CRgb3DbSnSET4B+TZMn/sp72UJw79boqjDPPsxh5v5oOusfnEclNXj8mvTAHoY4T I4IoiUADK8a/VZlg8Pcn9yyazOZ/uo42t7+7MApIloybh1mrnxGIN59irjZ1QMUareIA P1Jh7gcGMiZ8ia/tc2ltHCo5PWeW1CuRbAfJ+xsl6Up/Kd//0riN5xhMxn5yhFcQJjtW e8cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=Z6wMa8Qnzo3eXBmC/3WSOjxL8GTI/OCh7ZtmfhJjomM=; b=gJjqGsGi+ypPMO0YCpSKBx38KFGa/D2+fP3W5UOgMJ+isfE+eBmdZVLyxkXpVY6Mwj Wc97J/74UCxNaKVjt6GMeWDnFDXeguShg8Rd3zJFS2V+zHphdjWFfzPmqKZByU9FU/mL MtXqcvPUe7NvE+8CTrHn/w1zb6C3llnrQFSW9Xbs6rrD3ANr3DtZNTZeTgiY5j72S2W3 4f0JlFOyUsX4Imwxny4aVVZrzS6E0ViJCY2Nsl2kqEmmboaIWIGpUMLA+9IH9bL42rO/ 0JFnJYdRzWZX7mTtQV4KIc5osFI0oyAZQKzW8WuNviW5ih1qwf5uxpM64wcmn8T6p0yg QURg== X-Gm-Message-State: AIkVDXKMleytpCvmV7AhBf1fZnoku/OWUCae0e3mrB9daDic9Rch7oZSg01EnhRX5fZtPajp X-Received: by 10.200.35.246 with SMTP id r51mr25784616qtr.183.1485882603773; Tue, 31 Jan 2017 09:10:03 -0800 (PST) Received: from alvin.alvh.no-ip.org ([190.217.211.239]) by smtp.gmail.com with ESMTPSA id z23sm15800210qkb.30.2017.01.31.09.10.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 09:10:03 -0800 (PST) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 4F711F20; Tue, 31 Jan 2017 14:10:01 -0300 (CLST) Date: Tue, 31 Jan 2017 14:10:01 -0300 From: Alvaro Herrera To: Pavan Deolasee Cc: Jaime Casanova , Haribabu Kommi , Tomas Vondra , pgsql-hackers Subject: Re: Patch: Write Amplification Reduction Method (WARM) Message-ID: <20170131171001.wg7bc4pimfu6in6t@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-Pg-Spam-Score: -2.6 (--) 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 Pavan Deolasee wrote: > Two new APIs added. > > - CatalogInsertHeapAndIndex which does a simple_heap_insert followed by > catalog updates > - CatalogUpdateHeapAndIndex which does a simple_heap_update followed by > catalog updates > > There are only a handful callers remain for simple_heap_insert/update after > this patch. They are typically working with already opened indexes and > hence I left them unchanged. Hmm, I was thinking we would get rid of CatalogUpdateIndexes altogether. Two of the callers are in the new routines (which I propose to rename to CatalogTupleInsert and CatalogTupleUpdate); the only remaining one is in InsertPgAttributeTuple. I propose that we inline the three lines into all those places and just remove CatalogUpdateIndexes. Half the out-of- core places that are using this function will be broken as soon as WARM lands anyway. I see no reason to keep it. (I have already modified the patch this way -- no need to resend). Unless there are objections I will push this later this afternoon. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers