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 1pMYRQ-0007LJ-7z for pgsql-general@arkaria.postgresql.org; Mon, 30 Jan 2023 17:59:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pMYRO-0007pu-BZ for pgsql-general@arkaria.postgresql.org; Mon, 30 Jan 2023 17:59:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMYRO-0007pj-0f for pgsql-general@lists.postgresql.org; Mon, 30 Jan 2023 17:59:38 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMYRK-0003LT-Pe for pgsql-general@lists.postgresql.org; Mon, 30 Jan 2023 17:59:37 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 7E2A73200A97; Mon, 30 Jan 2023 12:59:30 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 30 Jan 2023 12:59:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1675101570; x=1675187970; bh=N RJKsFwyEDR7FHaGdY/bX0HDoUuX4mzJIAGySVwhsMc=; b=EoRjoH4+WjGoovvit 0KaUblSkHd/YFEEI6cb7Igi9wYVU3z2g5+/iitFRpsRH/xpWFNo3RZ1Rwh7pV7XS Ktg6KgACP8tCODyYeropmKOxsCztxMa0l6N4iZvr/2M7L4KGrvmowRyCefGCs0+H V39uq8Tc4ks/70NJTYItn0mwZ4pSeT2Va4g/t7RprUtBnQ9mr/dTUFQBAy3NRuBK 6QWxx7TM4j0c8LAJAqzy5gn5adE1si0352GgT1k89hbSYSn3hG4I0cCjA+FvHH8g rtU0jHyT1CuKTzkP1hvhaz4bmkuStbh/Np63rYUJ3K5tvKz3dipXpoh1SdAtISBk mXF8Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefvddguddtlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvfevuffkgggtugfgjgesth ekredttddtjeenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghr rhgvsegrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepvdektdffud fftdffffehfffhjeejhffgieeuueekjeekfffgudffhfduffffueevnecuffhomhgrihhn pegvnhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdho rhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 Jan 2023 12:59:29 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id A1F4E99; Mon, 30 Jan 2023 18:44:37 +0100 (CET) Date: Mon, 30 Jan 2023 18:44:37 +0100 From: Alvaro Herrera To: "jacktby@gmail.com" Cc: pgsql-general Subject: Re: How could I elog the tupleTableSlot to the fronted terminal? Message-ID: <20230130174437.ldgmku7zvfihej77@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202301302306168304483@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Jan-30, jacktby@gmail.com wrote: > For example, I use "insert into t values(1)"; and I 'll get a tupleTableSlot, > > And Now I want to get the real data , that's 1, and then use elog() func > to print it. Could you give me some codes to realize that? futhermore, > what If the data type is text or other types? What do I need to change? Maybe have a look at the 'debugtup()' function. It doesn't do exactly what you want, but it may inspire you to write the code you need. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "All rings of power are equal, But some rings of power are more equal than others." (George Orwell's The Lord of the Rings)