Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tolt1-00F9JD-TR for pgsql-bugs@arkaria.postgresql.org; Sun, 02 Mar 2025 16:09:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tolt2-004kgR-N4 for pgsql-bugs@arkaria.postgresql.org; Sun, 02 Mar 2025 16:09:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tolt2-004kff-Ec for pgsql-bugs@lists.postgresql.org; Sun, 02 Mar 2025 16:09:51 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tolsz-000XJI-0A for pgsql-bugs@lists.postgresql.org; Sun, 02 Mar 2025 16:09:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 522G9lOi3189042; Sun, 2 Mar 2025 11:09:47 -0500 From: Tom Lane To: armandnortjee@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18829: RAISE NOTICE appends 's' to string in PostgreSQL 17.2 In-reply-to: <18829-2ed4d964795b3b57@postgresql.org> References: <18829-2ed4d964795b3b57@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Sun, 02 Mar 2025 14:18:55 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3189040.1740931787.1@sss.pgh.pa.us> Date: Sun, 02 Mar 2025 11:09:47 -0500 Message-ID: <3189041.1740931787@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > In PostgreSQL 17.2, when using the RAISE NOTICE command with a string > variable, the output incorrectly appends an extra 's' to the string value. The substitution marker in plpgsql RAISE strings is just "%", not "%s" as it is in C, so this output is expected. That wasn't the best design perhaps, but it's impossible to change it now. > This issue does not occur when running the same code in earlier PostgreSQL > versions (e.g., PostgreSQL 16). You are quite mistaken about that. It's been like this since the beginning of plpgsql. regards, tom lane