Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAhMg-0004eO-HI for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Nov 2017 19:10:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1eAhMg-0007ud-3w for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Nov 2017 19:10:50 +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 1eAhL8-00056R-IP for pgsql-hackers@postgresql.org; Fri, 03 Nov 2017 19:09:14 +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 1eAhL5-00061j-9Q for pgsql-hackers@postgresql.org; Fri, 03 Nov 2017 19:09:14 +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 vA3J94HW010311; Fri, 3 Nov 2017 15:09:04 -0400 From: Tom Lane To: Alvaro Herrera cc: Robert Haas , Pg Hackers , Maksim Milyutin , Amit Langote Subject: Re: Proposal: Local indexes for partitioned table In-reply-to: <20171103173042.rgtuwowlfbv54sae@alvherre.pgsql> References: <20171103173042.rgtuwowlfbv54sae@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Fri, 03 Nov 2017 18:30:42 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10309.1509736144.1@sss.pgh.pa.us> Date: Fri, 03 Nov 2017 15:09:04 -0400 Message-ID: <10310.1509736144@sss.pgh.pa.us> 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: >> It might work to build the new key in a context that's initially a >> child of CurrentMemoryContext, then reparent it to be a child of >> CacheMemoryContext when done. > That's another way (than the PG_TRY block), but I think it's more > complicated with no gain. I disagree: PG_TRY blocks are pretty expensive. 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