Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iVJKm-0003Tg-3U for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Nov 2019 17:55:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iVJJl-0002bG-Ls for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Nov 2019 17:54:05 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iVJJl-0002b8-3o for pgsql-bugs@lists.postgresql.org; Thu, 14 Nov 2019 17:54:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iVJJg-0004Dy-9W for pgsql-bugs@lists.postgresql.org; Thu, 14 Nov 2019 17:54:03 +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 xAEHrrLU003809; Thu, 14 Nov 2019 12:53:54 -0500 From: Tom Lane To: Michael Paquier cc: Andres Freund , Manuel Rigger , PostgreSQL mailing lists Subject: Re: REINDEX CONCURRENTLY unexpectedly fails In-reply-to: <20191114080855.GG1910@paquier.xyz> References: <20191113154837.mgz2rnl6d7k6tas7@alap3.anarazel.de> <12383.1573660748@sss.pgh.pa.us> <20191113163851.e2enkdpvd3nrobst@alap3.anarazel.de> <19198.1573663534@sss.pgh.pa.us> <20191114080855.GG1910@paquier.xyz> Comments: In-reply-to Michael Paquier message dated "Thu, 14 Nov 2019 17:08:55 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3807.1573754033.1@sss.pgh.pa.us> Date: Thu, 14 Nov 2019 12:53:53 -0500 Message-ID: <3808.1573754033@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Michael Paquier writes: > On Wed, Nov 13, 2019 at 11:45:34AM -0500, Tom Lane wrote: >> Oh, I like that idea. Keeps applications from having to think >> about this. > That's interesting, but I would be on the side of just generating an > error in this case thinking about potential future features like > global temporary tables, and because it could always be relaxed in the > future. I don't find that very convincing. If there's a reason to throw error for global temporary tables, let's do it for that case, but that's no reason to make the user-visible behavior overcomplex for other cases. It might well be that we can handle global temp tables the same way anyway (ie, just do a not-CONCURRENTLY reindex on the session's private instance of the table). > I am actually wondering if we don't have more problems with other > utility commands which spawn multiple transactions... Indeed, but there aren't many of those... regards, tom lane