Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flKEJ-0000en-0T for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Aug 2018 20:29:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1flKEH-0001tn-Fh for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Aug 2018 20:29:49 +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.89) (envelope-from ) id 1flKEH-0001tg-8n for pgsql-hackers@lists.postgresql.org; Thu, 02 Aug 2018 20:29:49 +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.89) (envelope-from ) id 1flKEE-0007J6-F0 for pgsql-hackers@postgresql.org; Thu, 02 Aug 2018 20:29:48 +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 w72KTadR005608; Thu, 2 Aug 2018 16:29:36 -0400 From: Tom Lane To: Robert Haas cc: Andres Freund , Peter Eisentraut , Andrey Klychkov , Victor Yegorov , PostgreSQL Hackers Subject: Re: Alter index rename concurrently to In-reply-to: References: <1531767486.432607658@f357.i.mail.ru> <1531828116.497549417@f411.i.mail.ru> <6cf6b35f-b730-60fc-bab7-82699dca59ed@2ndquadrant.com> <10678.1533072318@sss.pgh.pa.us> <4aadd527-9986-36bd-978c-2300a95e7aec@2ndquadrant.com> <20180801193616.gi7mfs4kn5kggamf@alap3.anarazel.de> Comments: In-reply-to Robert Haas message dated "Thu, 02 Aug 2018 15:57:13 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5606.1533241776.1@sss.pgh.pa.us> Date: Thu, 02 Aug 2018 16:29:36 -0400 Message-ID: <5607.1533241776@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > On Wed, Aug 1, 2018 at 3:36 PM, Andres Freund wrote: >> What precisely are you proposing? > Inserting AcceptInvalidationMessages() in some location that > guarantees it will be executed at least once per SQL statement. I > tentatively propose the beginning of parse_analyze(), but I am open to > suggestions. What will that accomplish that the existing call in transaction start doesn't? It might make the window for concurrency issues a bit narrower, but it certainly doesn't close it. regards, tom lane