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 1j2eo2-0006RT-VZ for pgsql-bugs@arkaria.postgresql.org; Fri, 14 Feb 2020 17:31:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j2eo1-0004rD-FG for pgsql-bugs@arkaria.postgresql.org; Fri, 14 Feb 2020 17:31:09 +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 1j2eo1-0004oz-0z for pgsql-bugs@lists.postgresql.org; Fri, 14 Feb 2020 17:31:09 +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 1j2enu-0007vL-Am for pgsql-bugs@lists.postgresql.org; Fri, 14 Feb 2020 17:31:07 +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 01EHUxxv002697; Fri, 14 Feb 2020 12:30:59 -0500 From: Tom Lane To: "David G. Johnston" cc: RekGRpth , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand In-reply-to: References: <16258-f5218e29662078f7@postgresql.org> <16670.1581693636@sss.pgh.pa.us> <17339.1581694592@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Fri, 14 Feb 2020 10:14:53 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2695.1581701459.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 14 Feb 2020 12:30:59 -0500 Message-ID: <2696.1581701459@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "David G. Johnston" writes: >> пт, 14 февр. 2020 г. в 20:36, Tom Lane : >>> Doesn't sound like a bug to me. The sending backend will only >>> send out notifications when it goes idle > Does a non-interactive psql session ever go idle mid-script? Sure. "idle" here means that the backend is done with the current command from the client. I think the OP's problem largely stems from trying to do two transactions in one simple-query message, which is an abuse of that feature to begin with. (We've discussed taking away the ability to do that altogether, and while I've resisted that on backwards-compatibility grounds, it might well happen someday.) regards, tom lane