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 1tEOAk-0074DA-DZ for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 07:33:46 +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 1tEO9j-006BC3-46 for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 07:32:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEO9i-006BBt-Mc for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 07:32:42 +0000 Received: from mail-qv1-xf2f.google.com ([2607:f8b0:4864:20::f2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEO9g-003Elf-9X for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 07:32:42 +0000 Received: by mail-qv1-xf2f.google.com with SMTP id 6a1803df08f44-6d43b396c9bso12322466d6.0 for ; Thu, 21 Nov 2024 23:32:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732260758; x=1732865558; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/SZNaVKtigOnkOLlf84SEOtGxTOzPmD7MmJrJ4ASelE=; b=GBiP+2Q1cqrC9mSqgc4knagAUSHptdwYWq/Kgp5HsjkMgtSf8N7aYlvEFD7Uj5qiAr bD/zk0WMpN9C7pLRgBkxiwPYZYOdJKTFlYPHmNdP5C+2HtwisMiu1M96UclLqLRDRG69 zDxu1qH0u3zWSBVl2yA2XqEVEamWbWkVuK4ItlEzRTYrs2Xlzz2j4L81DoerZAScVl8b 2P4NGZeCFyaxJ/OucCOr1hrKSHESxeOAMOUFERBoLHjY4nbjkUqaM59dXGfOmTjTiNzi cBx7MVBX/iltohldx7pY91tUVf+MiJRURnoZRYgUFywhtC6EUFM65whVk7Qz5+TPqovN cOeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732260758; x=1732865558; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/SZNaVKtigOnkOLlf84SEOtGxTOzPmD7MmJrJ4ASelE=; b=levA4fNqnGNaLL60Xo5EW1QZoNgOe/czjkttsTFdkQwHvdOuIo7qj4Kacrn9FejO0V IMbkQzam7bUrGmwslyTtyZTga+6RMBV4gO5X8ujlKJYMVjflr9hWwLdgq6WvMLf/ag82 TFG+neXmH/Q88Qw66nvKifApKiZlhdCjV+pBMTq8mF4KKxUwfVhnjZxy7URGCGv6G4jb 4IdKwACjYOFF6kFwG9OfjzvqY/r5qW/yOsv1jbrztvXki4pZnS+9i8oA4ZVGoJq6Neom zxhaImSqhX5cLkH9lnY/mwuGEyz7HE308I9o4YNnbbcEkv/W8l/wHYIBqxrcN0546y9O pgsQ== X-Gm-Message-State: AOJu0Yyn5ROIXGgAXvAaynOwvvAJRovq3LKuH6xqJzDz2RVIct1w3NWm h4o7nJxLsccwMmyEY0hafr4txoPzpKNsLm7LIup/nC7vZbiUKg31qPGmBiYzyZUtoUWN2VjT9Bb NZEkRl64GreXhpH2lXavgKt5qEaY= X-Gm-Gg: ASbGncu54JtHPcoH92F4qzCurEb1Q3e0deVCLVVv+mwwzr0/0oMa5x9dcQEk0SF6H6d qiVxVif29IdhRqCtFgW4zcNA+4n2rxdpw3iJSgIEKzX/7Wy0= X-Google-Smtp-Source: AGHT+IHaUhx3Po3wFIy8xPPg7FUr5d3x5hoNGEXdzX+UlTwACRmII5nwpmq0UxxLmIzTzSBV6Fzd1xrd4BqYyHZoxPI= X-Received: by 2002:ad4:52c7:0:b0:6d4:c6d:1805 with SMTP id 6a1803df08f44-6d45137cb4fmr24295526d6.43.1732260758446; Thu, 21 Nov 2024 23:32:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jethish Jethish Date: Fri, 22 Nov 2024 13:02:27 +0530 Message-ID: Subject: Re: PostgreSQL Log Info To: "David G. Johnston" Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000002a6acc06277b634f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002a6acc06277b634f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi David, If an select query is fired I need the query returned values needs to be logged in my PostgreSQL log file. For example if a select query returns 5 rows I need the same in the log file On Fri, Nov 22, 2024, 10:49=E2=80=AFAM David G. Johnston wrote: > On Thursday, November 21, 2024, Jethish Jethish > wrote: >> >> Is it possible to log the rows returned by a query in the PostgreSQL log= s? >> > > As a practical matter, no. That said, given one can get row contents int= o > the server log in various ways, what is the use case for why this > capability is thought to be needed? > > David J. > --0000000000002a6acc06277b634f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi David,

If an select query is fired I need the query returned values= needs to be logged in my PostgreSQL log file.


For example if a select query ret= urns 5 rows I need the same in the log file=C2=A0


On Fri= , Nov 22, 2024, 10:49=E2=80=AFAM David G. Johnston <d= avid.g.johnston@gmail.com> wrote:
On Thursday, November 21, 2024, Jethish Jethish <jethish777@gmail.com> wrote:
Is it possible to log the rows returned b= y a query in the PostgreSQL logs?

As a practical matter, no.=C2=A0 That said, given one can get row conten= ts into the server log in various ways, what is the use case for why this c= apability is thought to be needed?

David J.=C2=A0<= br>
--0000000000002a6acc06277b634f--