Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvQEj-0002ax-QI for pgsql-general@arkaria.postgresql.org; Sun, 29 May 2022 21:14:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nvQEi-00040g-Cm for pgsql-general@arkaria.postgresql.org; Sun, 29 May 2022 21:14:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvQEi-00040W-2G for pgsql-general@lists.postgresql.org; Sun, 29 May 2022 21:14:08 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvQEe-0005dJ-3n for pgsql-general@lists.postgresql.org; Sun, 29 May 2022 21:14:07 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7D5EF5C0098; Sun, 29 May 2022 17:14:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 29 May 2022 17:14:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1653858843; x= 1653945243; bh=VJgFSdJkoKSuHK2oNrFq7Tt8bqIgnYZCpm/ang3qvwc=; b=M /KLZwzaf2yqbP4O9jgpgDKs9FsSfAMwWHngVK2oUIfJOxvwhkGC+bjUfBVUgm3a8 b65AiV4J7GQPnJJHysjO7cuFThglGQlXe127kN0hh6itERh+pfwUNMkFwOklJF0c 4W4i+CaFF3qpWbqU9o6iPd2by2YaM7Y3ALvbNQz1tL5kFWy4FkPoT+b3vrEKHG6h oLpVF3jjmdfQyE6sdpjY27NSSsFa5kbK4RO5zEaq/lXaKTk1HEqsq/aSTbu5/0Hp AUpA8T4COAvm14kxCOGNe7ivqNenBJ3F4PrlBb/I9N1wGT4F43MT6uhlTJTgv8BY mYz4OE6he1495HWPXsFpQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1653858843; x=1653945243; bh=V JgFSdJkoKSuHK2oNrFq7Tt8bqIgnYZCpm/ang3qvwc=; b=hXFY7kLybzoy1in9s UX+fR0d19YzDu0hYLmSKjAUg0e74ViGN6Qh+aAr4vBgfofLcbmgPkGMh7fCnwSAI aRjJ3Omo8NeUkpmC8K+zzA40MuplaC7POSjcZ/Xe3JoD6OF6v6RPslqsO3K9XsbA O2FMn1p9TbHvTHqtICgC91ZZHD4uZIzQ31lW8Kw9Zo2F3Nmqt3FMqOHSWL+6imkf 98bNC71csG5L1hVYnne+j9hbYRLh2UxFo+ay+9uK4E9lKlgHZvEqVhcmsFHSyQcY +6kh9VCDR1SNvvqAitrELEJKJAKg1pnM5dIhK+Gz1iXwTRlqROrEhkNI+AsAOw1W 5wOqg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeeggdduheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeevvdekiefhudfhhfdtkeelgeffudeigfetjeegfffg hfetfeelledugfelleegveenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 29 May 2022 17:14:02 -0400 (EDT) Message-ID: <6d14b1d1-fb8b-87d3-bdf8-d3c93c8bbb7b@aklaver.com> Date: Sun, 29 May 2022 14:14:02 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: psql 15beta1 does not print notices on the console until transaction completes Content-Language: en-US To: Alastair McKinley , "pgsql-general@lists.postgresql.org" References: From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/29/22 13:59, Alastair McKinley wrote: > > > > From: Adrian Klaver > > Sent: 29 May 2022 21:47To: Alastair McKinley > Hi Adrian, > > I am running the function "select test_notice();" from the psql console > with psql/server versions 15beta1. > > In psql 15beta1, the notice appears only after the function > returns/transaction completes. > > If I execute the same function from psql 14.3 and server 15beta1, the > notice appears on the psql console immediately as expected, before the > pg_sleep() completes. > > It's reproducible for me, I just double checked it. Yeah, I see the same thing after using the new psql. > > I think Tom was able to reproduce this by the sounds of his response? I have not received that post yet. I do see it in the archives. I had already tried: \set SHOW_ALL_RESULTS off which is supposed to restore to previous behavior, but it did not lead to the 14.3 result. > > Best regards, > > Alastair > -- Adrian Klaver adrian.klaver@aklaver.com